I am having the same issue. Have 16 Sonos devices - six Play 5's, ten Play 3's and a connect AMP. I keep having to reauthorize Pandora every day. This never happened before until the past two weeks where I have noticed every single day. I reported the issue to Sonos and sent them a diagnostic. My setup is perfect. once I reauthorize Pandora through the Sonos app I am fine. SONOS techs passed the buck to Pandora as they see no issue on their side. I use the free Pandora.
Tanner. I saw this solution posted in the Sonos community forum site and on a follow up it did not address or solve the issue.
Moderator Edit: Changing title for clarity
Pandora Update 9/22/21: Hi everyone! Thanks for posting your experience. We're working closely with Sonos to help resolve this.
Sonos has requested some additional information to help in their investigation. If you're new to this thread, please include the following info with your post:
Thanks for your understanding and patience in the meantime.
Hi @josebe! Thanks for posting.
I've created a ticket to pass on to our engineering team for further investigation. Can you let me more about how you usually connect to stream music on your Sonos?
Are you using the Pandora app or the Sonos Controller app?
If you are using the Sonos Controller app, are you streaming from your mobile device or from a computer?
Thanks!
Tanner...this is a more extensive reply. Typically I use the SONOS app from my iphone 12. I also have the SONOS app running on a PC with the latest version of the Windows operating system (64 bit). I rarely use the SONOS app in windows and rely primarily on the app on my iphone.
As of 7:01 PM this evening I tried to use the SONOS app on my cell phone and got the same message "Unable to play Pandora - access is denied". I had the same message this morning but once I reauthorized it I was able to play music all day on SONOS. I read something on another post in the SONOS user forum about free Pandora having a 4 hour timeout feature? Not sure if this has anything to do with it.
Ill have to reauthorize it again tomorrow morning.
Thanks!
Thanks for the follow up, @josebe. I've passed on the details to our engineering team. I don't have any troubleshooting to offer at the moment since I believe that our usual steps will not help in this case.
I'll follow up in this thread when more information is made available to me.
Thanks for your patience in the meantime.
I have the same problem. What do I do?
Update. I downloaded the Pandora app from the App Store and was able to play one of my stations without any issues.
Tried the Sonos app and got the message unable to play Pandora access is denied.
Thanks for the follow up, @josebe! I'll let our team know and reach out to the Sonos team as well.
Hi @jgdesigns01! Thanks for posting your experience.
I've included your info on our ticket and will update this thread with new info as it's made available to me.
It looks like @josebe was able to use the Pandora app with their Sonos device without issue. I would recommend this as a workaround while we continue to investigate.
Thanks for your patience.
Just to clarify. I did not cast the app to the Sonos speakers. I played music on my phone.
Thanks for the clarification, @josebe! 🙂
I have this problem too. 😞
We're having the same issue. Need to reauthorize every time we turn on our Sonos.
Yep, same here, having to re-authorize Pandora every day or two, was working great for years until this last week.
Any update? it seems like the the authorization (token) sonos is using for Pandora is invalidating or not refreshing properly. This is a major pain as the rest of my household can not play radio stations until i go into a sonos app and re-authorize my pandora account. This is happening at least daily, if not more frequently.
I am having the same issue using the sonos app on my android samsung S8 phone. This just started happening a few weeks ago
At the risk of jinxing myself, this *seems* to be working for me now! I gave up re-authorizing and instead disconnected Pandora entirely from within the Sonos app. I then added it back. It’s been working as expected ever since.