Sonos App not working in MacOS Golden Gate Beta

When I look for an update in version 17.2.4 it now shows: Sonos-system is up-to-date

👍🏻

I had the same challenges as others, it couldn't find my system. I uninstalled everything related to Sonos from my Mac—I simply gave up.

I just downloaded the app again, and—voilà—everything worked after two seconds 🤗

Thank you shadowyman, i tried your second suggestion, "/Applications/Sonos.app/Contents/MacOS/Sonos", with success on my MacOS 26 install and it worked!

​@SweeTart 

This is no longer necessary. There is an update that fixes this problem. Either select check for updates in the controller, or download the new macOS controller from the download page.

I am going nuts with this. I updated my firmware on my Asus zenwifi router and now I cannot get the desktop controller to work. I ran all the terminal commands I turned off my firewall, I restarted the Mac. I don’t dare upgrade from Tahoe yet because I'm sure that will break everything. I still get the error about the firewall no matter what. And terminal doesn’t work. Any suggestions?

​@maria_3 

Did you download the new version? 

BTW...I have an ASUS AiMesh. I’m running macOS Golden Gate.

I just downloaded the newest version of the app and it worked (the installed one didn’t).

FIX: Sonos Desktop Controller Cannot Discover System After macOS 27 Update — SonosLibraryServer Permissions

After updating to macOS 27, my Sonos desktop controller stopped discovering my existing Sonos system.

Environment:

• macOS 27
• Sonos Desktop Controller 90.0-82050
• Apple Silicon MacBook
• Existing Sonos system operating normally from other controllers

Symptoms

Launching Sonos normally produced the following error:

“Your computer’s firewall setting has changed. Your Sonos controller can no longer connect to your Sonos system.”

The error appeared despite the firewall and Local Network permissions being correctly configured.

Reinstalling Sonos, checking firewall settings, resetting permissions, and following the usual troubleshooting recommendations did not resolve the problem.

An Interesting Discovery

Launching Sonos directly through Terminal worked perfectly:
/Applications/Sonos.app/Contents/MacOS/Sonos

 

This successfully discovered all my speakers and restored full controller functionality.

However, launching Sonos normally through Finder continued to fail.

I confirmed this behavior using:
open -a Sonos
And:
open -n /Applications/Sonos.app

 

Both failed.

I could even run two instances of the identical Sonos executable simultaneously: one functioning normally and the other displaying the firewall error.

This strongly suggested a macOS application-launch or privacy authorization issue rather than an actual network connectivity problem.

The Solution That Worked

While examining the Sonos application bundle, I discovered an executable named SonosLibraryServer.

It is located at:
/Applications/Sonos.app/Contents/MacOS/SonosLibraryServer

 

I then performed the following steps:

1. Opened Finder and navigated to Applications.
2. Right-clicked Sonos.app and selected Show Package Contents.
3. Opened Contents → MacOS.
4. Located the SonosLibraryServer executable.
5. Opened System Settings → Privacy & Security → Full Disk Access.
6. Discovered that SonosLibraryServer was listed but not enabled.
7. Enabled Full Disk Access for SonosLibraryServer.
8. Returned to the application bundle and manually launched SonosLibraryServer.

This immediately triggered the macOS permission prompt that had previously failed to appear:

“Allow Sonos to find devices on your local network?”

I selected Allow.

Result

The Sonos desktop controller now launches normally through Finder and successfully discovers my entire Sonos system.

Terminal is no longer required.

Possible Explanation

This appears to involve macOS privacy authorization for one of Sonos’s supporting executables.

The main Sonos application already had Local Network permission enabled, but manually launching SonosLibraryServer triggered an additional authorization request.

It is not yet clear whether enabling Full Disk Access was essential or whether manually launching the helper executable was sufficient to trigger the missing permission prompt.

Full Disk Access and Local Network access are separate macOS permissions, so I would not assume that granting Full Disk Access is universally necessary or advisable.

Nevertheless, this exact sequence resolved the problem on my Mac.

Recommendation to Sonos

It may be worth investigating how SonosLibraryServer initializes and requests macOS Local Network authorization, particularly following macOS upgrades.

The existing firewall error is potentially misleading because the underlying issue may involve application privacy authorization rather than firewall configuration.

Hopefully, these findings help others experiencing the same problem.