Mobile Remote Control unresponsive

[just1man]

Hello,
Thought I would give the Mobile Remote a whirl on my Android. Simple to set up and connect - but tried in 2 different mobile browsers (Firefox and Chrome) and seeing odd behavior:
1) multiple login requests pop up one after the other
2) Screen flickers noticeably, almost as if it is trying to refresh continually
3) The buttons weren't responsive at all.

Hope it's a simple fix on my phone settings - i like the ease of use and setup

edited to add - updated to the latest version yesterday.

[bll]

Don't know what's happening here.

I tried changing the password in BallroomDJ, and the mobile remote control says "unauthorized",
but it's not going into a loop.

In mobile firefox, I went to "settings / delete browsing data", and that cleaned up the password.

I tested with Firefox in Linux and Mobile Firefox and they work fine.

Microsoft Edge on Windows 10 keeps asking for the password multiple times, but after entering the id/password twice,
I hit cancel for the next password prompt and it works.

Firefox on Windows seems to do the same thing, asks for the password multiple times.
I think it's asking for the password for each HTML element.
I suspect a reload might work after entering the password once.

Tried firefox on windows a second time after clearing the browsing data, and it is fine. Cannot repeat the multiple-password issue.

Try it again, see if you can make it work.
If there are still problems, I can get debug data from you.

[bll]

I saw the problem on mobile firefox. I had to clear the browsing data.
If it happens again, I want to try just closing that tab only without clearing the browsing data.

[bll]

I going to switch the authentication method used to a simpler method.
Hopefully that will clean up the issues.

[just1man]

Thanks for the fast responses

Deleting browsing history did fix the multiple login issue, but the app itself is still not working. Sent you a video link of what it is doing via email (from Help menu in app).

[bll]

I changed the authentication method used by the browser, but the problem is that I cannot reproduce the
issue reliably, so it is hard to tell if it has been resolved. I think it is fixed with this change (version 3.30.5).