Well, that took some doing but it worked! I now have a working 16.1 app on my phone which will be staying right were it is until Sonos sort out the new one with at least  working Local Library management. I just hope that Sonos don’t put up any barriers to using 16.1 until that happens

We really shouldn't have to go these lengths to be able manage our own music

...and AlexPermit, I forgot to say thanks

You’re welcome!  I’m happy to hear it worked.

I presume that now I have the ipa file, putting it back on the phone would be very easy (I have iMazing) if I DO accidently let the app update? 

TBH, if they sort local library searching, I’ll put up with the rest of the app as I’ve not has some of the issues that others are seeing with connectivity etc, but the old app is a breath of fresh air by comparison (and that’s something I never thought I’d say). 

Yes it should be easy.  I have also added the ipa file to Imazing’s local library to be triple sure. I’m only afraid that I (or my wife) will accidently update the firmware. I’m not sure what that would do to the old app.

I also agree about the old app.  As Joni Mitchell said, “you don’t know what you’ve got till its gone”.

Take a look at the SonoPhone app - it’s better than S2 was in many ways.

I’ve got both the Sonophone and Sonopad apps and they both work flawlessly for finding and playing local library files, but, of course, they don’t do any of the things the Sonos app can do around controlling your system.

Hey!

Just did this for kicks and to make sure I have a backup copy just in case and tossed it into iMazing. It does indeed say 16.1, but the icon is still black, at least under the Windows iTunes display…….same for anyone else?

The file size is def smaller then the new one, and opening it up an Pacifist suggests that it’s the App from March, so I assume it worked.

--Brian

Mine has reverted to the gold icon on the phone but was black in iTunes, so seems to be Ok. Certainly works exactly as you’d expect on the phone (and as it did before the nightmare began). I wonder how long it will be before Sonos stop 16.1 working? 

Well that didn't take long

What’s your firmware? All of mine are still on 16.1.1, build 78152020.

Good to hear @ainsley002! A little added color for anyone considering this route: you can install  the Sonophone app side-by-side with the new Sonos app and both will work. That gives you the stability and functionality (plus reduced frustration) of Sonophone while you play with the (slowly improving) new Sonos app.

16.2 as I’d already done that update, unfortunately. I presume that's the problem although it did work fine for almost a whole day !  Just caught up, I imagine. 

So at least we know that there’s no technical reason WHY Sonos can’t bring that functionality back to their App. If another App is doing all of it before their App, they can’t say its impossible :-P

That’s unfortunate.  Your assumption about 16.2 is probably correct.  Strange it gave you a grace period before complaining.  It makes me wonder if the system somehow “phoned home” to discover the “incompatability”.  Did you turn off “check for updates” in the Sonos App when you originally installed it?

I’m guessing you already tried closing the Sonos App then restarting it.

What Alex said: 16.2 feels like a “pusher” to get people on the new 80.x software? Because that 16.2 came out like the next day after the new App launched right?

Good detective work @AlexPermit and @CronoCX! FWIW, I’ve been running the v16.2 firmware with a mix of v80.x apps (iOS, iPadOS) and v16.1 apps (Android) and have not been nagged to update … yet.

My impression was the v16.2 firmware re-introduced the ability to edit alarm settings. YMMV.

So messy. Ugh. It makes me sad that people can’t just do the simple thing of hearing music on their system. It’s a big thing for me. I’m also helping a friend with an issue that I’ll be posting about today. It’s crazy how broke things are :-(

Yes, updating off and several restarts tried. Now I have the 16.1 .ipa file I might try deleting 80 off the phone and putting 16.1 back on just to see what happens

Did you have 80 on your phone when you were running 16.1 and came accross the update message? 

That is quite telling.  I can’t imagine Sonos would have introduced a 16.1 block on IOS but not on Android.  Then again, I can’t imagine they would have released v80 in the state it was in 

To be clear, I meant the 16.2 firmware, not the Sonos App. 
 

@AlexPermit Yeah. I can’t believe they did either. Yesterday I was helping a friend who has been plagued with issues since his accidental update and it was the first time I’d used the new App and wow it’s garbage top to bottom. I find it more confusing to use than the old one. And the persistent “now playing” pop up is annoying as hell. 

I had a brief encounter with it, and I agree.

I take it from your post you are the “local tech support” in your circle of friends  What would they have done without you around 

If you happen to have a spare IOS device laying around and was willing to put in the time, it would be interesting to see if you get the same problem @ainsley002 has.

No, I deleted 80 and rebooted the phone before putting 16.1 back on.