Skip to main content

Right off the bat: This is an issue that can only be addressed by the Sonos Mac app development team, because something is wonky with their build/release process such that the latest version of the Sonos S1 app for Mac (as downloaded directly from https://support.sonos.com/en-us/downloads ➡️ https://www.sonos.com/redir/controller_software_mac ➡️ https://update-software.sonos.com/software/72ynP0v9lu/Sonos_57.22-59130.dmg has no valid CFBundleVersion or CFBundleShortVersionString value specified within the app’s Info.plist file.

 

This means for all intents and purposes macOS has no idea what version of the app is installed —which then means that any central software management software, like any macOS MDM for systems management, cannot accurately report on or update the Sonos app in a trackable fashion.

 

This oversight can be confirmed by looking directly at the Info.plist file within the app package, and comparing the most-recent release to a previous version of the app. Or, for a nice GUI experience, using an app lke Apparency to open both apps side-by-side, which clearly shows the issue:

 

We’ve filed tickets on this 07661650] and waited more than a couple months to see if the dev team is ever looped in, but tbh describing the ins-and-outs of how Mac app versioning works —and explaining that no, downloading the same app disk image over and over again will not somehow add in info that is missing from the app bundle itself— isn’t something that the support team is (or really needs to be) aware of…

 

But it should definitely be something that Sonos’ developers and/or internal IT should be very familiar with so it’s disappointing this hasn’t been noticed and perhaps a silent re-release of the app build 57.22.59130 pushed out which adds a valid version key back into the app bundle…

Hi ​@ZGM 

Welcome to the Sonos Community!

Thanks for flagging this - I have informed an engineer and we have created a support ticket to investigate this issue. The ticket has been tagged against your existing case.

They would never be able to submit the app to the Store like this, but of course that is never going to happen anyway, for so many reasons.

Thank you ​@Corry P —we appreciate the followup. Fingers crossed there will be an updated build with a valid version number soon! 

Hi ​@ZGM 

I have been informed that this will be resolved with the next S1 update, which is due very soon. 

Thanks again for flagging!

Hi there ​@Corry P we noticed that from within a 57.22-59130 Sonos S1 app if we run a check for updates it can retrieve a new 57.22.65130 version which has a valid CFBundleVersion (yay!) —however downloading the Sonos S1 app directly from  https://support.sonos.com/en-us/downloads ➡️ https://www.sonos.com/redir/controller_software_mac still returns the Sonos_57.22-59130.dmg disk image file.

 

Is there some alternate download link we could point to get the updated disk image, or is it still a work in progress having it published outside of the auto-updater flow?

 

Thanks!

Hi ​@ZGM 

Sorry for the delay - I have been on holiday.

I cannot say what the circumstance was when you checked, but I just checked now and the file seen when right-clicking the S1 macOS download link now is Sonos_57.22-67080.dmg

So, it seems correct now.

I hope this helps.

Hi ​@Corry P hope it was a good vacation!

We were also able to download the Sonos_57.22-67080.dmg file from the S1 download link now, however this version has a new issue when compared to the 57.22.65130 version which was available through the S1 app’s auto-updater, namely that while there is now a valid CFBundleVersion listed, there is also an invalid CFBundleShortVersionString showing ??:

Invalid CFBundleShortVersionString in version 57.22.67080

Compare this to the 57.22.65130 release which had a valid CFBundleVersion defined and no CFBundleShortVersionString (which is fine and acceptable Mac versioning behaviour):

Valid CFBundleVersion in version 57.22.65130

This is a continued problem because most Mac MDM software management tooling uses the CFBundleShortVersionString, when available, to track the version of the app installed. If the CFBundleShortVersionString is not available then the MDM will use CFBundleVersion for tracking.

 

In this situation, where the CFBundleShortVersionString exists but is non-numeric and non-comparable with the CFBundleVersion, we’re basically back where we started with version 57.22.59130 and its invalid versioning 😞 

Hi ​@ZGM 

Thanks again for flagging - I shall forward this on to the same person as last time.

Many thanks!

Reply


Terms & ConditionsCookie settings