Saw this on two different machines after update from 26.6.2 to 26.7. Sonos app launches to black window with white SONOS near top and the colorful pinwheel just spins. Tried reinstall after deleting all caches and preferences. Tried reinstalling Rosetta 2. Same behavior. Nothing in the logs - last entry shows “current network - :192.168.16.100:”.
Anyone else having this issue?
I don't do apple but there have been a few recent posts on some setting needing tweaked.
Thanks that thread was helpful. MacOS 27 seems to have the same issue as the new MacOS 26.7. The Sonos app does work if you launch it from the terminal.
As I posted in the other thread. I didn’t have a problem with macOS 26.7 using either Sonos or Sonos S1 controllers.
Sonos App launches natively. No Terminal required.
The current Sonos desktop controllers no longer need Rosetta 2. They run native on Apple Silicon now. Are your sure you have the latest?
MDCR
Modern: 90.0-79210
Legacy: 57.23-80060
That's the version I’m on 90.0-79210. I tried reinstalling as well. It works fine if I run /Applications/Sonos.app/Contents/MacOS/Sonos from Terminal. If I launch from the App Icon, I get stuck on this screen with the mouse pointer changing to the color pinwheel. It does this on my Mac Studio and on my MacBook Air, both on MacOS 26.7
That is strange. Previous macOS 26.x versions had problems with local network permissions. In settings, Privacy & Security → Local Network. Toggle Sonos off/wait a few secs/back on, fixed it. Also look in settings, Network → Firewall, Options. Locate Sonos and make sure it’s set to ‘Allow incoming connections’. If it’s not there, add it.
I haven’t needed to do anything at all after (or, before, honestly) on my Mac M1 after updating to MacOS 27, and running the Sonos S2 software. When Sonos released the update that
There’s definitely something odd going on, on your Mac. Mine is fairly vanilla, but Sonos software continues to work without issue.
That is strange. Previous macOS 26.x versions had problems with local network permissions. In settings, Privacy & Security → Local Network. Toggle Sonos off/wait a few secs/back on, fixed it. Also look in settings, Network → Firewall, Options. Locate Sonos and make sure it’s set to ‘Allow incoming connections’. If it’s not there, add it.
Tried both of those. Same issue. It happens on two different computers - a MacBook Air M4 and a MacStudio M4.
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.
following are done:
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.
+24So, 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?
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.
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.
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.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
