the new Sonos ios app update is TERRIBLE! DO NOT UPDATE!

This morning I discovered that the latest update on my Android phone has ruined my SONOS system.  I use SONOS for 2 things -  BBC Radio and HiFi quality music from my music library.  I do not want voice control, nor any streaming service such as Spotify. 

I now cannot see my music library - SONOS, what are you playing at?  Please reissue the old app so we can choose which we want.

Fortunately one of my devices (Amazon tablet) has not updated, but I'll be stuck if it does.

@Ken_Griffiths 

Ken , thanks very much for your help.  I should have been clearer - on my Android phone, which updated automatically overnight, the new app is virtually useless.  Fortunately, my Amazon tablet (also Android) has not updated.

Are you sure smbv2 is currently required? The Sonos help docs say it is recommended, but not required. But agree with Sonos use v2.

https://support.sonos.com/en-ca/article/use-a-nas-drive-with-sonos

Surprised of this change without a firmware update on the speakers but TIL.

It does seem to not really be finding my network stuff (grayed out on Android) but I see no point in working to solve that problem when the app DOESN'T EVEN LET ME SELECT/ARRANGE WHAT SONGS PLAY WHEN. That is the PRIMARY function of the app, so if it doesn't do that, it is non-functional broken garbage.  Gonna see if I can roll it back when I have some time later today.

Sigh....At least this destructive "update" only happened on my phone so my desktop PC and laptop can still actually manage what I want to listen to.

I'm honestly baffled as to how conscious human beings could release this, supposedly thinking this was a thing to control what their products do. IT IS NOT. Seriously, WTF??

IIRC Support for SMBv1 is available in the S1 App only, because that App development, in real terms, was put on hold at the S1/S2 split. As far as I am aware, S2 then moved forward with SMB v2 (or higher) shares only.

SMBv1 had caused problems along the way for some users after the vulnerabilities were highlighted and ‘http’ sharing was introduced for use by both S1/S2 before, or around, the time of the split. This uses the Sonos Library Service installed with the Desktop controller. I’m guessing that controller may be retired in the coming months as it’s hinted that the new ‘catchall’ Web App will supersede it. 

So it clearly makes very little sense to include the vulnerable SMBv1, or ‘http’ sharing protocols in the new App for a local library - it will (IMHO) only be supporting the SMB v2 (or higher) shares only, particularly in the longer term.

What I am unsure about, at the moment @Bumper, is if ‘http’ library shares setup via the Desktop controller are ‘perhaps’ being supported temporarily. I haven’t had time to test that, but either way, that sharing method will ‘highly likely’ go when the Desktop controller App (Sonos Library Service) bites the dust. 

I’ll just add the above is my own opinion and thoughts about what the plan might be for local libraries, but I do not see any indication that Sonos plan to take local library access away from us. I think that will turn out not to be the case. We shall have to wait and see.

This app is sooooo bad, half of it doesnt work and thr other half I dont need, my playlists have vanished, i cant clear current playlists. DISASTER 

My very expensive speakers are just useless bricks now.

Had no choice to update as the speakers would not work without an update.

Listen sonos these are my speakers that I paid for, can you stop telling me what I want and need,  Butt out and stop harvesting data from us all, just give us a controller that works and let us enjoy the sound quality that we paid for  stop trying to be Google and control everyone, let the customer decide what they want.

I don’t think they removed smbv1 from the speakers yet, it was still a part of s2 and there was no firmware update to remove it from the speakers which make the actual connection with your nas. So if you had an smbv1 library set up prior to updating your app it should still work as the share is handled by the speaker right?

The removal of smbv1 is a big problem for some people because there is a Sonos library indexing bug that will crash indexing on smbv2 shares. This doesn’t impact all people, but it is a known bug for a year or two and Sonos hasn’t bothered to fix it. So when smbv1 is gone, some owners won’t be able to index due to the bug.

See this thread

No indexing for some and no search for everyone, doesn’t look like they give a crap about local library users but just my opinion.

I just very happily uninstalled this new version and re-installed the S2 controller version 16.1 by following the steps here

https://www.androidpolice.com/roll-back-android-app-older-version/

That's for Android, not sure how to do it on iOS. Don't forget to turn off auto-updating!

Yay I can run my system from my phone again!

Your speaker updates are a different thing from your updated controller app. You can return to the older version of the controller, and your speakers will still be updated and should work okay (mine are). Good luck!

Absolutely agree - thankfully I tried the new app on my iPhone before upgrading any other device so at least I can still play MY OWN MUSIC. This ‘upgrade’ is almost magnificently awful. I wish to de-upgrade. If Sonos doesn’t fix this mistake it might it might be last straw for me with Sonos. 
 

E2A: I spoke too soon - upgrading on one device has apparently had a knock on effect across the board. I can no longer access my music via Sonos any device. Much, much sadness.