They have been open in saying later versions of the App will restore/fix functionality that was missed of broken.

I’ve updated and at least the queue is back. I hope the fix the My Library.

That is all well and good but I guess I will pass on installing the update since I don’t trust that after installing I will gain anything useful and run the risk of actually removing what functionality I do have.

You brave soul. Do post as to whether you now have access to your music library.  Thanks.

Today’s new app update is perfectly safe. You’ll be forever on Unfixed Island if you don’t jump aboard the good ship Update, bound for the land of Almost As Good as S2 One Day...

Access to your library has more to do with the dropping of SMB v1 than anything else.  If you haven't disabled SMB v1 on the share that your library is stored on, then Sonos isn’t going to see it no matter how many releases they put out. 

That is your choice but we know the developers at Sonos are working hard to solve the issues.

“Fix this mess Sonos!!!! Fix it!!!”

<Sonos releases app with fixes>

“No way I’m loading a new update, I don’t trust Sonos to fix things!!”

<me dies >

Not sure what this means. But on my Android tablet I still don't have access to my NAS library (which I have on the desktop and old app).

I also don't see a way to browse the library (only links in favorites which aren't accessible).

After I lost access to my library I contacted Sonos support (after a 70+ minute wait on the phone). While the rep looked at the diagnostics I had submitted she basically said there was nothing that could be done until such time as Sonos released an update. She offered no solution to resolve the problem. I’m running version 16.2 on their S2 OS. 

Never use the app on my phone (though I suspect that Apple automatically updated; need to disable that setting). Unfortunately I did update the app on my desktop which is where I always launch Sonos from. Whatever you do don’t update the desktop app.

No offense to the support people at Sonos, but depending on their experience level, they could just be reading a script.  There’s more than a few threads on here discussing how to disable SMB v1 on Mac/PC/NAS.  After that is complete, you may need to download the PC/Mac app from Sonos.  After that, try adding your share from the manage menu, if it is not there already.  Then check your Android App.  If it doesn’t show, close out the app completely and restart.  If it still doesn’t show, reset the app, then restart and choose “Connect to an existing system”.

Probably more work than it should be, but that’s the series of steps that has worked for others. 

I don’t use the app on my iPhone, only the app on my PC which is where the problem exists. I did try to follow the steps listed on several of the threads to no avail. Just frustrating that Sonos broke what I considered a functioning application (at least on the PC) all because they needed to meet a deadline to support their new headphones. Really enjoy the Sonos speakers I have but would not invest another dime in their products given this major screw up.

The App on the PC has not gone through the same rewrite activity as the Android/IOS one which may indicate that the issue you have is that you need to upgrade from SMBV1 to SMBV2 or SMBV3.

Why don’t you try it on your phone and see if it helps you? 

To be fair, the SMB v1 stuff has nothing to do with the headphones.  They did that because of long running threads started by security obsessed “Sonos owners” (it’s in quotes because I’m not sure some of them were actually owners) who had enough time to constantly post about the issues with SMB v1, despite there being no documented cases where a Sonos system was compromised due to SMB v1.  There were also several questionable click-bait trade articles equating the SMB v1 usage with an entirely different Sonos security “risk” due to some 3000 or so Sonos users leaving their system with no active firewall (or on the modem side of the firewall), completely vulnerable to outside access (and still, the use of SMB v1 wasn’t compromised).  

After 6/4 download I still can't Trueplay my my Era 300/Arc/Sub setup. 

I already posted it elsewhere but I want to highlight my quick feedback on this latest update (iOS app version 80.02.04).

Official release notes state the following among other updates:

• Added “play next” and “add to end of queue”
• Added sleep timer settings

My observations (with iOS app, local music database on NAS):

• “play next” and “add to end of queue” only works for individual Songs or whole Albums. I would like to have this function for all songs from specific Artist or Genre. I am sure it worked like that in S2 until this 80.0 apocalypse...
• I still cannot edit queue (remove songs, change songs order)
• Sleep timer should be available from “Now Playing” screen - three dots icon at the bottom right. I can see this icon there but it always appears inactive (greyed out) and tapping does not produce anything. 

Can anyone confirm this?

Just on sleep timer - for me, the three dots bottom right brings up the various Play Next etc options, as well as Sleep Timer…

hmm interesting, thank you. sending a screenshot of how is looks at my end

three dots icon is there but it does not react to tapping...

Have you tried closing the app down fully, then rebooting your phone..? Bit of a last resort but maybe the best way to get the app to load up properly..??

I did and still the same. Also tried to reset the application. Looking for others with the same problem. I am going to test this with my spare iPhone SE tomorrow.

P.S. Just learnt in the other thread that three dots icon is inactive when Music Library is a source...

Play next…”something went wrong. Try again”, though it does actually play the track next 🧐 A bit of an own goal there!

Three dots and sleep timer work for me with streamed music but when playing from local music library the three dots are inactive and greyed out.

I took your advice and found a good step-by-step procedure in one of the threads. I’m on Windows 10 running the Sonos Desktop app. 

peterlip wrote:

I’ve fixed mine after talking to support, but this is not something for the average user.  I hope there’s an easier way, as I found it a bit of a chore, and I work on computers all day.  Here’s how I did it in windows 11..

1. Make sure SMBv1 is disabled by doing the following:
2. Launch the Control Panel by typing Control Panel in the Windows search box.
3.  Click Programs in the list and then select Turn Windows features on or off under Programs and Features.
4.  Ensure there is no checkmark in the box next to both SMB 1.0/CIFS File Sharing Support and SMB 1.0/CIFS Server.
5. If you had to disable it, it may require a reboot after you deselect, and hit OK.  Mine fortunately wasn’t selected.
6. Create a share on the folder that your music is in, and give a user permission to use it.
7. I created a local user using instructions from here: https://support.microsoft.com/en-au/windows/create-a-local-user-or-administrator-account-in-windows-20de74e0-ac7f-3502-a866-32915af2a34d   But apparently you can use the user you’re logged in as (I couldn’t, it didn’t work for me).
8. With a user ready, right click the folder containing music and select Properties
9. Select the Sharing Tab
10. Hit the Share button, and make sure the user you want to use is in the list with at least Read access, and hit the Share button.
11. Back on the sharing tab, it will show the name of the share as \\<computer name>\Music      (or whatever the share name is (mine was called TheLibrary))  Hit Apply.
12. This share name is what you type in the sonos app when you are adding your music library.
13. fin

Still don’t understand why disabling the SMB V1 didn’t just allow the path to be shared? Anyway I am back up and can once again access my music library.