Skip to main content

Since a recent update to Sonos Build: 84163110 (MacOS Sequoia, Macbook Pro M4 MAX), I am seeing a lot of performance issues, interruptions and all-out failure.   I generally am using the Spotify App, with my speaker group selected, which is configured from Sonos.

In between these failures and jittery behavior (which includes app playing but NO sound), I am seeing callouts to api.branch.io -- some of them fail, this causes Sonos to freak out, lose my speaker configuration/group.  Not good.

This application needs to be able to operate without all these external dependencies being “live” all the time.  I can observe this behavior live, when I manually cut off access to api.branch.io with filters and Sonos again freaks out.

Is anyone else experiencing this?  I’m not sure this is the best software implementation with these dependencies.

The app on your PC is nothing more than a remote. Why should an update of the app cause drop outs in your system?

This is my question, too.  Why?  I have been observing the traffic between Sonos app and the Internet and there are many external callouts.  I guess we’ll just have to see. 

The context of my query is larger, as Sonos works to improve the product, there may be others who experience these same issues.   From what I can gather, Branch’s services provide for deep linking and analytics, into applications.  Streamlining mobile engagement, enabling seamless navigation across devices and platforms. So there appears to be a lot going on, under the hood.

My personal position is that this app (system) should also be able to run and function competently in an isolated environment, too; granted, that must be mitigated for updates.

 

Terms & ConditionsCookie settings