Enthusiast I

Answered

yet another unwelcome change

13 replies
229 views
Translate All

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

very annoying!

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

R

RhonnyAnswer

Prodigy III

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

R

RhonnyAnswer

Prodigy III

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

Translate

T

Tom4103Author

Enthusiast I

Thanks for your quick reply!

Translate

AjTrek1

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

Translate

Together Everyone Achieves More = T.E.A.M.

Airgetlam

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.

Translate

Bruce

rosswells127

Prodigy I

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.

Translate

rosswells127

Prodigy I

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.

Translate

Airgetlam

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.

Translate

Bruce

rosswells127

Prodigy I

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.

Translate

Airgetlam

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.

Translate

Bruce

I

Ian_S

Prodigy III

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.

Translate

Show more replies

Sign up

Login to the community