The following is not intended as an exoneration of Sonos. However I know some will take it as such. That being said let’s begin….
People in this Community are questioning why Sonos doesn’t roll back to the app version prior to this new release. There is a plausible reason why that may not be possible. One of the two may shock you. However if it was the execution used to launch the app update...right or wrong “it is what is.”
There are two ways to execute (push out) an update:
- COMMIT
- ROLLBACK Contingency Plan
COMMIT means exactly what you are probably thinking that when executed there is no going back. Of course, its execution typically means a high level of confidence and/or that any bug (for lack of a better term) can be fixed over an acceptable time frame.
The time frame to correct the issues may not be inline with customer expectations; but information is published (when needed) to outline the time-to-resolution for clients. Companies will weigh the bottom-line affects and deem them acceptable.
Auto manufacturers for example have produced cars that have a failure rate for a certain component. However, they deem the cost of a re-call too expensive/disruptive and will handle each failure via warranty. Hopefully not at the cost of lives.
ROLLBACK Contingency Plan is quite self-explanatory as well meaning that if the push-out is faulty it can be rolled back to the previous version. However, executing a roll-back could have detrimental effects upon newly released products and/or products/features already in the pipeline. Thus making a rollback contingency plan unpalatable. Use your own imagination to discern what Sonos product(s) might be affected by this scenario.
Apple for example frowns upon rollbacks of its software but it’s not entirely impossible; if you are willing to take the risk. If you upgrade to a new iOS then realize you prefer the previous version, you can possibly go back to an older version of iOS. However, the downgrade process is complicated, with multiple steps, strict parameters, and potential pitfalls such as bugs and security fixes no longer being available. FYI, restoring an iPhone from a backup is not the same as a downgrade.
Below is a brief description of Commit vs Rollback. The complete article can be found in this link
Getting back to Sonos. I don’t know what their thought process was or under which of the two parameters they implemented the app update release. If I were to guess I’d say COMMIT; but that’s pure speculation.
What I can say is the app is stable for me and others who have posted. Constantly blaming the app for everything is not productive and won’t help with your frustration. You have to be willing to go the extra mile and look elsewhere. That may take the form of:
- Running a system diagnostic and contact Sonos Tech Support *
- Seeking advice in the Community
- Updating device software
- Updating router firmware
- Setting static IP Addresses for Sonos components
- Changing WiFI Protected Access levels
- Changing network configurations that are known to cause Sonos problems
Take this information for what it’s worth. If it helps fine. If not…then continue down your own path.
Good Luck!
* I realize there are longer than normal waits. I waited 30 minutes and didn’t like it…but I was able to resolve my issue.
