Skip to main content
Contributor I
March 31, 2023
Answered

Sonos controller for Mac failing to update with Mac OS Ventura 13.2.1

  • March 31, 2023
  • 48 replies
  • 9919 views

After updating to Ventura 13.2.1, the Sonos Controller Application tries to update, but fails repeatedly. Is this a known issue? If so, what is the solution?

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.
Best answer by LordAttilas

I had the same issue for some time in MacOs. Yesterday I found that you need to authorize the “Sonos Installer” under System Settings → Privacy & Security → App Management. Once I allowed it I was able to use the auto update from the Sonos app itself.

 

Previously I was uninstalling and installing the new one from the website.

48 replies

Contributor I
November 22, 2023

Thank you! I wish Sonos would make Best answer by LordAttilas an article that can be found by searching their support website. Instead, their instructions are to uninstall and then install again, which is cumbersome.

ctoryu
Lyricist I
November 24, 2023

Tried all of the suggestions listed above and finally just installed the latest download over the existing app and no more updates needed.

I have never been able to get the Sonos App to update on an iMac.

 

Now to figure out the channel issue, system keeps dropping out on me.

Airgetlam
November 24, 2023

On the Mac, you should  authorize the “Sonos Installer” under System Settings > Privacy & Security > App Management.
Or, just delete the current file, and download a fresh copy from Sonos, making sure to ‘Connect to existing system’ when prompted.

The former is a much more permanent solution, the latter will work this time, and you’ll need to continue to repeat that process for each subsequent update.

Bruce
Lyricist I
December 2, 2023

I had the same issue for some time in MacOs. Yesterday I found that you need to authorize the “Sonos Installer” under System Settings → Privacy & Security → App Management. Once I allowed it I was able to use the auto update from the Sonos app itself.

 

Previously I was uninstalling and installing the new one from the website.

finally the solution I have been waiting for so long - THANK YOU!!!!

Lyricist II
December 11, 2023

MacBook Pro 2018 with Ventura 13.6.1, tried LordAttilas solution of granting access in App Management. It didn’t work for me. I had to Delete my existing Sonos app and download the new one. That worked very well. First time I opened it it had all my Sonos system information.

I didn’t realize there was an Uninstall program in the Sonos App. I just deleted the app manually in the App folder. I couldn't find on Apple Support where the uninstall program for an app might. I had to go to the Apple Community pages. Looks like Sonos has the same attitude towards current assistance -- Go ask the community. Anyway, thought I’d share what I learned. Here’s what the Uninstall looks like:

 

 

Enthusiast I
December 15, 2023

Hi,

I, too, have this problem and have added the Sonos app to the relevant list in MacOS App Management Settings, but this does not fix the problem.

I see plenty of references here to adding the Sonos Installer to this list, but this app does not appear in the Applications Folder on my Mac.  Am I missing something or does it go by another name?

I am reluctant to uninstall the Sonos app for fear of losing some part of the existing set-up e.g. Favourites, Sonos Playlists etc, which we would not be a welcome by-product. 

 

Enthusiast I
December 15, 2023

Just downloaded the latest Sonos app (v15.11) and update problem is resolved and I retained all my Favourites, Playlists etc,  However, I still do not have any app called Sonos Installer in my Applications folder and therefore expect to have the same problem when the next update come through.

Can anyone clarify what I am doing wrong and/or where I can find Sonos Installer to add it to the App Management whitelist in System Settings.

Thanks.

Lyricist II
December 15, 2023

I went through the same thing. I couldn’t find the uninstall for Sonos so I just put the App in the trash and downloaded the App again. I was relieved that my existing system and all the related stuff was still working with the updated Sonos app installed.

I don’t know why Sonos doesn’t make it easier and point out things like where the uninstall is located.

Click on Sonos in the top menu line. Uninstall is in that pull-down menu. There is not a separate install/uninstall program. The install is simply that notice in the .dmg package that you download that says to drag the app to the Applications Folder. 

 

Airgetlam
December 15, 2023

Just as a note, uninstalling the app is not an issue. All of the settings for your system are stored on the speakers, not in the app. If you feel the need to delete and reinstall, just make sure that you choose ‘join existing system’ when presented that dialog.

Bruce
Enthusiast I
December 15, 2023

Hi Ken,

Thanks for your reply.  In my case it was not a problem of being unable to find the Uninstaller, but more that I could not see how to update the App Management list in Settings to include the Sonos Installer.  I have successfully added the Sonos app itself, which I selected from the Applications folder.  However, since there is nothing called Sonos Installer in that folder, you cannot grant it the permissions that MacOS seems to demand.

Other responders to this and similar topics have shown the Mac Settings with both apps appearing in the list, but I’m damned if I can see how they did it.  I did read that the Sonos Installer is a temporary program only appearing for the duration of the update.  That's sounds plausible, but if it is the case, I still cannot see how to get it to appear as an app permitted to delete other apps.

Quick  update - just before submitting this post, I decided to check the Mac App Management settings and Sonos Installer now appears in the list, albeit not enabled.  I certainly did not add it, so how it got there is beyond me, but I guess that should now solve the problem for future updates.