On a new phone I found that I can sign into my (docker) instance OK, but there is no follow through on setting up the device as a mobile in HA, and as soon as I close the app, I'm right back to square one (entering the URL).
I removed the App config on my existing phone as a test, and see the same issue.. constantly signing back in from scratch on both Android phones now.. So I'm lead to suspect the recent Android app update. I can find no relevant logs in HA.
I've come to rely on the mobile tracker for a bunch of things.. but i get no notifications or GPS tracker data without the app registering correctly, so very keen to figure this out.
I do have the OIDC integration (bypassed for spp login), so.. maybe? that's involved, but before I go and disable all that i was hoping this was a known issue/change and I've just failed to search properly... anyone seen this?
No I'm trying to add it as a different device - but i can totally see that some kind of Samsung device transfer feature/behaviour could potentially be screwing things up - thanks for the tip will follow up if it fixes it
Edit - nope didn't help..
Signing in with the mobile app is indistinguishable from signing in via a browser, the app doesn't follow through with the device registration at all, it's like it's still in setup mode - if I hit the back button it goes back to the very initial step (that you'd see straight after install).
It was the OIDC integration. When I disabled that, the devices onboarded normally. Reenabling the OIDC integration doesn't break the app once it's set up.
Last time I disabled and reenabled it, I had a bit of a drama with all my browser cookies but this time it was no problem at all.. so that's a positive.