Hi all,Since a recent macOS update, the Sonos desktop app on my Mac can no longer connect to my system. The Windows desktop app, running in Parallels on the same Mac and the same network, works perfectly.SetupMacBook Air M2 (2022), macOS Golden Gate 27.2 Sonos for Mac 17.2.5 (build 90.0.82050), downloaded fresh from sonos.com S2 system: 4 players (Play:1, 2× SYMFONISK shelf gen 1, 1× SYMFONISK shelf gen 2), all on 27.3, just updated All devices on the same Wi-Fi subnet (10.0.0.x)SymptomsThe app first showed “Your computer’s firewall settings have changed…”. After a clean reinstall, setup (“connect to existing system”) fails with “Your Sonos product could not be found”.What I’ve checkedThe macOS firewall is off. Local Network permission: I removed the stale “Sonos” entry, relaunched the app, got the macOS prompt and clicked Allow. The toggle is now on. Clean reinstall: I removed the app, its prefs, caches and Application Support folder, then rebooted. The app is listening on TCP 3400 (lsof). From Terminal, dns-sd -B _sonos._tcp lists all 4 players, and curl http://<player>:1400/status/zp returns data. Discovery and connectivity from the Mac work fine. Tailscale disconnected: no change. There is no other VPN or network filter on the Mac. The Windows desktop app 17.2.2 in Parallels (bridged networking) connects immediately and even ran the firmware update. After the update to 27.3, the Mac app still fails the same way.So the network and the players look fine. The problem seems specific to the Mac app on this macOS version.QuestionsIs the Mac desktop app still supported on current macOS, or has it effectively been retired in favour of the web app? Is there a known workaround or an updated build for Apple Silicon?Thanks!

Solved, thanks to kdowling’s pointer! The fix posted by St00pid in the “Sonos App not working in MacOS Golden Gate Beta” thread worked for me:Launching/Applications/Sonos.app/Contents/MacOS/Sonosfrom Terminal worked right away. It triggered the Local Network prompt that never appeared when launching from Finder.To make normal launches work, I opened Sonos.app → Show Package Contents → Contents/MacOS, double-clickedSonosLibraryServer, and allowed the Local Network prompt.Granting Full Disk Access was not needed in my case.The app now launches normally from Finder on macOS Golden Gate 27.2 (M2). Thanks Bruce and kdowling!

N

Niels_77

Trending Lyricist I

Answered

Mac desktop app (17.2.5) can’t find system on macOS Golden Gate 27.2 – Windows app in Parallels works fine

7 replies
98 views
Translate All

Hi all,

Since a recent macOS update, the Sonos desktop app on my Mac can no longer connect to my system. The Windows desktop app, running in Parallels on the same Mac and the same network, works perfectly.

Setup

MacBook Air M2 (2022), macOS Golden Gate 27.2
Sonos for Mac 17.2.5 (build 90.0.82050), downloaded fresh from sonos.com
S2 system: 4 players (Play:1, 2× SYMFONISK shelf gen 1, 1× SYMFONISK shelf gen 2), all on 27.3, just updated
All devices on the same Wi-Fi subnet (10.0.0.x)

Symptoms

The app first showed “Your computer’s firewall settings have changed…”.
After a clean reinstall, setup (“connect to existing system”) fails with “Your Sonos product could not be found”.

What I’ve checked

The macOS firewall is off.
Local Network permission: I removed the stale “Sonos” entry, relaunched the app, got the macOS prompt and clicked Allow. The toggle is now on.
Clean reinstall: I removed the app, its prefs, caches and Application Support folder, then rebooted.
The app is listening on TCP 3400 (lsof).
From Terminal, dns-sd -B _sonos._tcp lists all 4 players, and curl http://<player>:1400/status/zp returns data. Discovery and connectivity from the Mac work fine.
Tailscale disconnected: no change. There is no other VPN or network filter on the Mac.
The Windows desktop app 17.2.2 in Parallels (bridged networking) connects immediately and even ran the firmware update.
After the update to 27.3, the Mac app still fails the same way.

So the network and the players look fine. The problem seems specific to the Mac app on this macOS version.

Questions

Is the Mac desktop app still supported on current macOS, or has it effectively been retired in favour of the web app?
Is there a known workaround or an updated build for Apple Silicon?

Thanks!

kdowlingAnswer

The following thread started while Golden Gate was still in beta. It is long and it was also before Sonos released the Apple Silicon builds. Along the way, it was discovered that there was a code signing ID issue that was causing the app to not have local network permissions. That was rectified.

There hasn’t been any mention of it not working since. Until this last post in that thread. I don’t know what to make of it. But have a look:

Airgetlam

It up is working fine on both my intel based Mac Pro, and my M1 MacBook Air, for S2, so the answer to your first question is no.

The answer to the second question is yes…you just need to ‘update’ it. Honestly, I’d just delete the current version on your Mac, and then download a fresh version of the controller from Sonos’ website. Sonos took the extra step to recode it, even though it is semi-retired, to make it work on Apple’s own OS.

Translate

Bruce

Airgetlam

To be honest, I updated the installed version, and didn’t take that extra step of deleting first, but given that your account data is stored on the speakers, and not in the controller, you’ll be fine. The only danger is that the data gets erased when you perform a factory reset (on all speakers at the same time).

Translate

Bruce

Airgetlam

In case you don’t believe me :)

hmmm. Edit to delete screenshot, as it showed IP address in the Sonos part.

If you’re still having issues, I’d definitely call Sonos Support to discuss it.

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.

Translate

Bruce

N

Niels_77Author

Trending Lyricist I

Thanks Bruce. I actually did exactly that already: deleted the app and its prefs/caches, rebooted, and downloaded a fresh copy from sonos.com. It is the recoded universal build: 17.2.5 (90.0.82050), architectures x86_64 + arm64. Forcing it to run under Rosetta makes no difference either.

Could you tell me which macOS version you’re on? There are reports that the app stopped working with the release of macOS 27 (Golden Gate), so if you’re still on 26.x that would explain the difference.

Translate

kdowlingAnswer

The following thread started while Golden Gate was still in beta. It is long and it was also before Sonos released the Apple Silicon builds. Along the way, it was discovered that there was a code signing ID issue that was causing the app to not have local network permissions. That was rectified.

There hasn’t been any mention of it not working since. Until this last post in that thread. I don’t know what to make of it. But have a look:

Translate

Airgetlam

No, on the M1 I’m current, with 27.2. The intel based MacBook won’t update, but it is running as well, just not on 27.2

Translate

Bruce

N

Niels_77Author

Trending Lyricist I

Solved, thanks to kdowling’s pointer! The fix posted by St00pid in the “Sonos App not working in MacOS Golden Gate Beta” thread worked for me:

Launching /Applications/Sonos.app/Contents/MacOS/Sonos from Terminal worked right away. It triggered the Local Network prompt that never appeared when launching from Finder.
To make normal launches work, I opened Sonos.app → Show Package Contents → Contents/MacOS, double-clicked SonosLibraryServer, and allowed the Local Network prompt.
Granting Full Disk Access was not needed in my case.

The app now launches normally from Finder on macOS Golden Gate 27.2 (M2). Thanks Bruce and kdowling!

Translate

Sign up

Login to the community