Skip to main content
Trending Lyricist I
Nov 8, 2026 9:05 PM UTC
Answered

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

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

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

Thanks!

kdowling
kdowlingAnswer
Nov 9, 2026 6:05 PM UTC

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:

 

13 replies

Airgetlam
Nov 8, 2026 11:50 PM UTC

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
Nov 8, 2026 11:54 PM UTC

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
Nov 9, 2026 12:14 AM UTC

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
Niels_77Author
Trending Lyricist I
Nov 9, 2026 5:50 PM UTC

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
kdowling
kdowlingAnswer
Nov 9, 2026 6:05 PM UTC

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
Nov 9, 2026 6:25 PM UTC

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
Niels_77Author
Trending Lyricist I
Nov 9, 2026 6:47 PM UTC

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
Contributor I
Nov 17, 2026 9:07 AM UTC

Perfect fix !! Thanks.  Just after this I noted a Sonos update - not sure if that was them fixing it ?

Translate
Lyricist I
Nov 17, 2026 4:19 PM UTC

I encountered this exact problem today on a new iMac running macOS, set up using Migration Assistant. Sonos repeatedly displayed the firewall error and couldn't find my system.

My firewall was OFF, Local Network permissions were enabled, and all 12 Sonos devices worked perfectly from my iPhone.

I spent considerable time troubleshooting, including reinstalling Sonos, using its built-in uninstaller, resetting the controller, and removing the application's preferences, support files, and caches. Nothing worked.

I also confirmed that the iMac could reach a Sonos speaker directly through its IP address and discover all 12 devices using Bonjour. Clearly, the network itself was functioning.

The fix was manually launching SonosLibraryServer from inside the Sonos application package and granting it Local Network access. Sonos immediately began working.

This is an unacceptable software failure for a “premium” audio system. The application repeatedly directed me to troubleshoot a firewall that wasn't even enabled, while providing no indication that its own helper process lacked network permission.

Experiences like this are exactly why Sonos has developed such a poor reputation for its software. This wasn't some obscure configuration issue I created. It was a failure of Sonos's own application to handle a basic macOS permission, compounded by error messages that sent me through hours of completely unnecessary troubleshooting.

Thanks to the community members who identified the actual solution. It's unfortunate that Sonos customers have to do the troubleshooting the company should have done itself.

Translate
Smilja
Nov 17, 2026 4:58 PM UTC

​@TheWrongCrouton, If you come across this error again, try this:

  1. Remove the Sonos app
  2. Reboot the iMac
  3. Reinstall a fresh .dmg.

Sonos apps and downloads | Sonos (scroll down)

Translate
»And the world is like an apple whirling silently in space, Like the circles that you find in the windmills of your mind.« (›Windmills Of Your Mind‹ [1967]. Music by Michel Legrand ; English lyrics written by Alan & Marilyn Bergman)
Lyricist I
Nov 18, 2026 1:11 AM UTC

Additional reproducible case: macOS 27, Sonos desktop controller, false firewall error

I encountered this issue on November 17, 2026, on an Apple Silicon MacBook Pro after upgrading to macOS 27.x.

Environment

  • Sonos controller build: 90.0-67171

  • Existing multi-speaker Sonos household

  • UniFi-managed local network

  • Sonos explicitly permitted through the macOS application firewall

  • Failure began following the macOS 27 upgrade

Observed behaviour

Launching Sonos normally through the Dock produced:

"Your computer's firewall setting has changed. Your Sonos controller can no longer connect to your Sonos system."

However, launching the bundled executable directly worked:

/Applications/Sonos.app/Contents/MacOS/Sonos

The controller's logs confirmed successful SSDP discovery, UPnP event subscriptions, and connection to the existing Sonos household.

Relevant log messages included:

legacy_join_household_wizard:
Successfully joined household

SCZoneGroupMgr:
ZMState changed from WrongAPExistingHousehold to Playable

Global household state changed to
SOHouseholdStateConnectedPlayableZones

Despite this success, launching Sonos through the Dock initially continued to produce the firewall error.

Troubleshooting sequence

  1. Confirmed Sonos was allowed through the application firewall.

  2. Inspected macOS privacy permissions.

  3. Manually launched SonosLibraryServer from the application's Contents/MacOS directory.

  4. Observed permission errors when the helper attempted to create /Library/Logs/SonosLibraryServer.

  5. Launched the main Sonos executable directly, successfully connecting to all existing speakers.

  6. Retested the normal application launch, which initially failed but subsequently recovered.

The application now launches normally without requiring Terminal.

Possible cause

This behaviour suggests an issue involving macOS application-launch context, privacy authorization, or Sonos's bundled helper processes.

The logging permission errors are not sufficient to establish the root cause.

Recommendation

Sonos should investigate how the desktop controller and its helper processes request or retain Local Network authorization following macOS upgrades.

The firewall error is misleading when discovery succeeds through direct execution of the same controller.

No speaker resets, router changes, or firewall disabling were needed to restore functionality.

Translate
kdowling
Nov 18, 2026 5:57 PM UTC

It may or may not have helped, but you are running an old version of the desktop controller. The current version is 90.0-82050.

Translate