Please don’t hijack the thread. This is exclusively about the Mac client ignoring the disabling of the Auto-Update feature in the menu.
When I disable that option and launch Zwift, I expect it not to check for updates and force them down upon my client. After I’ve disabled the option and Zwift still forces the updates on me. This is a bug.
This is not about the mobile app disconnecting (which works fine in my case anyway, no issues at all with ZML).
For now, I’ve blocked any and all updates to Zwift on both my PC and Mac machines, because these new updates degrade existing functionality and introduce more bugs than they fix into my working configuration.
This is no different than most users should already be doing these days with Windows Updates, Mac System Updates, graphics drivers, AV updates or anything else that is updated on a regular basis. We’ve already seen the gross privacy violations and system instability that silent, background auto-updates do at the OS level (Windows 7 → Windows 10, McAfee/AVG/Comodo updates, NVIDIA drivers and hundreds of other examples).
Forced auto-updates are always a bad idea, since there’s no possible way that every permutation of every configuration and every condition can be tested on every end-user’s environment.
So, they’re disabled on my machines until I can fully and independently test and validate that they work without making my Zwift experience worse than the previous revision.
I can respect your desire to keep everything clean and current, Jon, but that’s not how it works elsewhere. Updates are not forced in many other pieces of software, including PlayStation, XBox or others. You can choose to accept them, or not, at your own peril.
There are some MMORPG/multiplayer online games that have mandatory updates, but that’s because they’re more of an ASP model than a client-server model.
Once my testing of new capabilities addresses the outstanding list of issues/bugs, I’ll consider upgrading to a newer version, but not until that time.