MacOS Tahoe 26.7 update kills Sonos desktop App

I don’t know what you could try next, except a call to Sonos Support. They might have something, if there are a lot of people reporting this problem.

i also have this problem. Launching from Terminal works OK.

following are done:

• in Firewall: removed sonos, added sonos.
• in Privacy => local network: deactivated and reactivated
• controller is reset
• uninstalling the app and it’s config (using AppCleaner)

they don’t solves the problem. 

only opening from Terminal works 

nohup "/Applications/Sonos.app/Contents/MacOS/Sonos" >/dev/null 2>&1 & disown

So, the question is, why does it work without issue on my Mac, and fails to work on yours? Have you called Sonos Support to discuss it, so they can look at the particulars?

When you speak directly to the Support staff, they have tools at their disposal that will allow them to give you advice specific to your network and Sonos system.

I can offer a theory: during the Golden Gate beta, the OS data for the local network permission was clearly getting corrupted for some users (see https://developer.apple.com/forums/thread/814226). That corruption may “stick” after the upgrade to the full version.

However the recent reddit thread regarding code-signing identity would imply a new/different problem.

Unfortunately I had to order a new Mac Mini myself (for my own app’s development) and when that arrives next week I can experiment further.

This thread is about macOS Tahoe 26.7. Since it is showing the same problem as Golden Gate, it seems the reddit post may be correct. That the code signing and bundle signing used two different identifiers in the new silicon builds. Why it still works for some and not others is a mystery. Left over setting from previous working versions?

The one I really don’t understand, is why running from the terminal works, and from the app icon doesn’t. In both OSs.

Just got off the phone after almost two hours with Sonos Support. They have “escalated to level three” and seem to think a patch will be necessary for OS 26.7 and 27 compatibility. Didn’t say when.

That’s good to hear. I don’t use the Desktop app but if it’s going to be out there it needs to work properly. Fix compatibility issues with the app regardless of platform and concentrate on features that matter to the public. In other words get the low hanging fruit/issues resolved and move on to the more important stuff. 

Codesigning is the issue.  The codesign fix from this reddit post addresses the issue.

Not that I use the Desktop app. However, Sonos needs to fix it since they have decided to make it available on Apple Silicon. Having to mess with terminal code in order for it to launch is not good.

Maybe only 2% of the over 1MM households with Sonos know how to change a code line 😂

Although strangely I have Apple Silicon in four iterations.

• M1
• M2
• M3
• M4

The desktop will launch on M1 and M4 (that’s a huge gap between Chipsets) but not at all on M2 and M3. Makes no sense. 🤔