I think that’s an indexing issue with some USB linked-to-router shared libraries which users were using SMBv1 to index their library before switching to SMBv2 to share it - its being investigated I believe, but in @BrianJG’s case I understand it’s a MAC shared library which I suspect is using the http protocol through the DCR and a user/share has perhaps not been put in place for the library folders - but that’s just a guess on my part.

There are at least some people who appear to have correctly configured a network share of a MacOS folder (Sonos able to connect to the share) and then run into issues during indexing. The linked thread below is one example. The person in this thread provides evidence suggesting their issue is related to cumulative length of the metadata being built up in the index. Not sure if this is specific to MacOS shares though or if its an issue for all very large libraries.

I don’t believe it was limited to  just usb libraries but if they haven set up the smb share correctly it’s definitely not this. 

Thanks for the cross-reference @osm, this is quite interesting! Two some-odd weeks back I made the observation that because the new app/new architecture is a blank-sheet-of-paper rewrite, lots of exceptions and corner cases are no longer properly handled. Those “lost lessons” will need to be re-discovered, re-debugged, and re-fixed before the new app/new architecture “just works” as well as the v16.1 app.

I suspect that many of the “works for me, broken for you” issues have such a root cause. Re-running the discover-debug-fix gauntlet will take time, as the difference between broken and working may be extremely subtle. In this case of this Mac user, it could be a single array in the v16.2 firmware that is not sized correctly; it could even be a new interaction between the v16.2 firmware and Sonos servers.

Those of us trying to help users diagnose and fix such “works for me, broken for you” issues can hopefully keep all this in mind when trying to help on these forums.

Are you high? The programmers, I’m positive, warned management that it wasn’t ready and full of bugs. Management pushed ahead with the rollout anyway. Now, we they are decimating their public reputation as far as quality product and service goes. I have posted many…not so stellar reviews…due to this recent change. This is not how you run a business. This is the entire reason you have beta testers. I’ve done several beta tests with Sonos and didn’t see anything regarding testing for this new interface or functionality testing. 

Today’s release has not fixed anything...actually, it is worse.

So updated just now and as well as all the ongoing issues, Sonos app now has a bug. Well of course it does, I just updated it and my system is up to date. It just keeps crashing even after cache is cleared. Thumbs up to Sonos. 

Hey @kevinboardley, are you on a Samsung device? I ask because I do not get that fabulous pop-up when the app crashes on my Android tablet.

IMHO, that pop-up is Peak FUBAR … and that’s a high bar after the past two months of fubar.

Dear Sonos: Don’t send me another update. Don’t expect me to download another update. DO NOT force another update on me…

Unless and until you have a finished product that, at the very least, includes all of the basic functions we enjoyed before you involuntarily recruited all of us for this science project two months ago sand still counting, with no end in sight]. 

I didn’t sign up for any of this. I’m a Sonos client because I want to play music without a lot of fuss. I had everything I wanted until early May 2024. I was a happy camper.

Now I’m not happy. Not a bit. Please fix what you broke. Please do not ask me to help you fix it. That’s not in my job description.

Thanks for your time and attention.

You don’t have to install the updates @chambolle, just disable the firmware auto-updates in the Sonos App and switch-off the App auto-install too for your controller device and sit back and wait until you personally decide to install the latest versions of the App/firmware.

Ken: At the moment, the auto-update slider is disabled [greyed out and inactive] in my Sonos app. I assume that means I won’t be forced to update. But at this point, who knows what’s going to happen next. 

My post was submitted in hopes the Sonos folks who initiated this string soliciting feedback are paying attention. And in hopes they’re going to hear us and have a sense of urgency to restore full functionality to our Sonos systems without considerable additional delay.

Which seems to be a vain hope thus far. 

So I'll just take pot luck then on when I should update to get back functionality unless of course I am forced to do so lest working functionality in the app is disabled.

I used to recommend Sonos. For some considerable time now, I warn people to steer clear. This is what happens when companies are driven purely by shareholder value. Customers go hang because you don't matter.

And I go to my desktop controller and sure enough functionality disabled until I update. I just thought of a very rude expletive.

Yes. Android. Started last night after update. Now I can't use it all. It hust crashes and closes within seconds of opening. 

Maybe this week’s app update will fix it.

Just tried support 40 minute wait, have to go to work.  Chat bot  reporting no agents available.

My questions will be, just in case anyone is looking here:  

1. Are they aware of this and if so, and they require a diagnostic,
2. how am I to send one given that the android app keeps crashing (edited: removed the desktop app still allows diagnostics)
3. If I update the desktop controller will I have absolutely no way of switching anything on or off other than unplugging from the wall?

What an unmitigated disaster. This sort of thing should spell either an end to a company or at very least its CEO in any economy that is managed even slightly for the benefit of the end consumer.

Yes they are definitely aware.

If you do a diagnostic collection post the details here so that the Sonos Team can pick them up.

I suspect that they are getting a lot of unsolicited diagnostics so it will help them to help you if you communicate the details. 

I have, you replied to it.  ************

Moderator Note: Recorded and removed diagnostics number. Modified in accordance with the Community Code of Conduct.

What a load of garbage. I haven’t had access to anything except Sonos Radio for two months. 

Now (7/19/24) it doesn’t work at all.  Come on, Sonos, talk to us!  What is going on & when?

Maybe it’s something local to you causing your App not to work?... It’s perhaps a little slow in some areas, but the App should now be working… it’s definitely working okay here.

Edit: If you can’t get the Sonos App to work maybe give Sonos Support a call. Here is the link to contact them:

https://support.sonos.com/s/contact

Since the ‘update’ a few days ago my app is even less responsive that it had been before.  Having to resort to using the buttons on the speakers to switch off when needed as the control doesn’t even register any speakers.  I suspect that a certain lack of responsivness will be a inherent ‘feature’ of the cloud based system that will never be resolved.  Promises, promises, promises that even when delivered never quite hit the mark.  Controlling my bluetooth speaker is more relaible and therefor emore ‘enjoyable’ as an experience.

Now (7/19/24) it doesn’t work at all.  Come on, Sonos, talk to us!  What is going on & when?

Maybe it’s something local to you causing your App not to work?... It’s perhaps a little slow in some areas, but the App should now be working… it’s definitely working okay here.

Edit: If you can’t get the Sonos App to work maybe give Sonos Support a call. Here is the link to contact them:

https://support.sonos.com/s/contact

Well aren’t you the lucky one.  Seems that this is not the case for many prople on the forums.  No local library I see.

I’ve uninstalled & reinstalled on my S22 twice… “Something went wrong with Sonos  Sonos closed because this app has a bug.  Try updating this app after its developer provides a a fix for this error.”  Message comes after it crashes.  I live in Washington, DC.  Also, I have wasted a lot of time with your support since the update.  Not looking forward to another round because I have a life.

Yes, I have a local SMBv3 NAS. That’s always worked in the new App. There’s Artwork missing on Android controllers, but it’s not too bad on iOS controllers.. as per below. I guess it would be nicer to view onscreen if the Artwork could be made available at some later point, though maybe not considered a priority at the moment, perhaps?

25,697 tracks..

FYI It’s a bug in the new POS app. A work around for some people is to not use local library music, only streaming.