No, it’s working okay here on iPad/iPhone/Android tablet - maybe try resetting, or reinstalling the App. If the issue persists, maybe try a different mobile or tablet, if you have one handy or can borrow one, just to test if that might work.

If still no joy after that then it maybe best to reproduce the issue(s) seen and immediately submit a Sonos system diagnostic report from within the Sonos App (if that’s possible), note it’s reference and contact/chat with Sonos Support Staff via this LINK and see what the Staff can perhaps suggest to help you to resolve the matter.

This began happening to me this morning on my iPhone. Was listening to music and paused the song for a half hour or so. When I tried to replay, the app had frozen and I had to close it. After that, it crashed each time I tried to open it. 

I am on the most current version and because I wasn’t able to open the app, my options were limited. Finally, I deleted the app and re-installed it. This did the trick. 

Thankfully, connecting back to my system was super easy - I was relieved that I didn’t have to recalibrate anything or add/configure my existing products. The app looked for my sonos system on my wifi, found it, and I’m back up and running.

Hope that helps anyone experiencing this issue.

Yes, reinstalling the app works but only temporarily. We are having to repeatedly delete and reinstall the app on our iPhones and iPads because the app crashes when trying to open it. The timing and frequency of the issue is random. Sonos and iOS device OS are current. App instability did not used to be an issue. 

I’m not experiencing this on my iPad. Which version iPad are you using? Which version of iOS?

One is an iPad Air 3 and one is an Air 4 both running iOS 18.2. We mostly use iPads to control the Sonos system.  

Is there any improvement if you reboot the player?

I can’t remember the last time the system components were rebooted so it’s probably been awhile. The current players being used are a One (Gen 1), a Five and an Arc Ultra. I can reboot them but it may be a while before I know if it made a difference or not so I may not have an answer for a while. 

When a controller starts up. It broadcasts a query, looking for a player. The controller “associates” with the first player to respond. Once associated, that player is used to communicate with the system. 

I’m speculating: If the associated player is frustrating the controller, causing the controller to crash, the controller will crash only when associated with that player. You could investigate this by systematically powering down a player while the controller is starting up.

Thank you, buzz, for detailing the communication sequence. I will have to experiment with that.