Skip to main content

Why is Sonos suddenly asking me every time to “ Sign in as owner to see Recently Played “?

very annoying!

It’s not a change, it’s a bug. (When I occasionally get the sign-in message appear, I just close the app and re-open it, which gets rid of the message, for me at least.)

https://en.community.sonos.com/controllers-and-music-services-229131/sign-in-once-a-day-in-the-new-app-what-is-going-on-6905138


Thanks for your quick reply!


Also I’m not having the issue on iOS nor Android?


Not that it’s overly helpful, but I’m also not having this issue so far, on several iOS devices, running iOS 18.0.1.


I have the issue on both my iPhone and iPad. As suggested in another thread on this topic I have reset the app on my iPhone and will see if that has any positive affect.
Ross.


My suspicion is that this issue potentially depends on the location/load of the Sonos authentication servers, which would explain the randomness and also why it only affects some users.
Sonos have previously already confirmed to me that they have had/having issues with their servers in the Asia/Pacific region which has been the cause of other latency issues with the new app.
Ross.


Certainly a possibility. If I were having this issue, I would submit a system diagnostic within 10 minutes of experiencing this problem, and call Sonos Support to discuss it. That way, they’d have hard data to look at, and pass on to engineering. Unfortunately, I’m not able to do that, since it isn’t happening to me here in the US’s Pacific Northwest.


Certainly a possibility. If I were having this issue, I would submit a system diagnostic within 10 minutes of experiencing this problem, and call Sonos Support to discuss it. That way, they’d have hard data to look at, and pass on to engineering. Unfortunately, I’m not able to do that, since it isn’t happening to me here in the US’s Pacific Northwest.

Unfortunately, Sonos support in this part of the world is really poor. Closest is Australia and in my experience their level of support isn’t great (I am being kind).
Ross.


Without any hard data, it only increases the possibility that there will not be any ‘solution’ found. Entirely up to you as to whether you want to submit hard data for them to hand over to an engineer, but I wouldn’t hold out a lot of hope, if they turn out not to be able to reproduce the error. Every code team I’ve been associated with looked on anecdotal (unreproducible) complaints with scorn. 

 


Of course Sonos has data. You think they won’t log all authentications? If they had any decent monitoring tools they’d be seeing a big uptick in logins to confirm it. It’s not like there are 16 different ways to start the app.

Like many things on the new app, it’s another really tedious lazy regression. 


Certainly tracking logins on the server side may not track what is happening on the client side, but then I don’t actually know what the issue is. Clearly, you seem to have better information and knowledge than I, so I’ll bow out. 


Obviously it doesn’t track the client side, but it’s a good indicator that something is amiss. I would expect as part of the last release (which received a couple of quick tweaks to fix other unintended regressions) they have tried to ‘improve’ the initial experience on startup, but have instead introduced another issue. So I don’t know, maybe they should revisit the code changes there to see if they can find the problem. It’s basic stuff, and sadly Sonos are showing no real sign of improving here despite all the rhetoric about ‘quality’. 


My suspicion is that this issue potentially depends on the location/load of the Sonos authentication servers, which would explain the randomness and also why it only affects some users.
Sonos have previously already confirmed to me that they have had/having issues with their servers in the Asia/Pacific region which has been the cause of other latency issues with the new app.
Ross.

Haven’t had a single issue with the new app since launch and everything has been fast for me the whole time. I’m in APAC.


Reply