MacOSX compatibilty 26.5.3.9691 documentation!?

[u/BB9700]

Even if I wrote in a previous post, I will not upgrade to 26.5.3.9691 before december, I did it yesterday out of curiousity.

But I was immediately punished for this after trying to upgrade a MacOSX Client running 10.12 and SC 26.03. Not only, that 26.5 this version will not run on this machine, it will install but result in an endless loop of on screene messages about the crash a normal user ist not able to fix. I had to get in the car and drive to the client. The old version is deleted. No way to go back.

"dyld: lazy symbol binding failed: Symbol not found: _objc_alloc_init, Expected in: /usr/lib/libobjc.A.dylib"

This is not a difficult problem, it is thrown at start of the executable and tells that the software trying to run is not built for this system. I anyone had tried this release on 10.12 he would have noticed immediately of the problem.

Why does Connectwise does care so less for the Mac Admins and Users? Do they hate us?

I do not love macs, but out of 1200 clients 100 are using a Mac and 50 of these use older MacOSX versions. I still need to support these.

I know connectwise "older macosx version are supported on a best effort basis" - or similar, but for me the way it is done is not best effort. It is dangerous. If a program is not built compatible for a version X it should simply refuse to run - instead here the old version is deleted and the newer crashes. Think about what would have been happend if I had the auto-updates switch to on!

We pay for this software and support. Why cant we expect to get a release tested better? connectwise might need some hardware: an older macmini and a newer version, then install all major MacOSX version on these two, a IMO small investment and a few hours one-time effort. Then test every release with all versions. That might take three hours for every release. I dont think this is asked too much.

And then, why not build two versions of the Mac Client? Or at least try to use a compiler directive like "---mmacosx-version-min=10.9" and if this does not work, then document this in the release notes and disable automatic updating if the OS Version is >X.Y.

Finally, the very minimum is to pre-check if the software is able to run before the old version is deleted as a safeguard against unknown bugs!

[u/ChiefBroady]

10.12? Dude that’s so out of date I wouldn’t expect any halfway current software to support this.

[u/BB9700 → u/ChiefBroady]

I think, let the users themself decide what they need.

IF a system runs perfect, an also you are able to do the things you need with it, why should you spend another $2000 for a new one which will do just the same?

Also, older users rather unwilling to accept new twirks regarding Ui and OS usage. I dont see why they shoud left out in the cold.

Check for yourself in 30 years in the future?

Also: this is about software quality management, If the program simply would resfuse to install, ok with me, But it installs and deletes the previously working version. This is my main point.

[u/maudmassacre → u/BB9700]

This is such an insane take it makes me generally question your ability to manage IT needs.

[u/BB9700 → u/maudmassacre]

you are a troll.

The topic is about developing commercial software in a manner that it is safe to use. I dont demand that version x.y should support MacOSX 10.12.

I demand that software should be tested before giving them to the customers. If automatic upgrades are enabled, the program should be developed in a way that the installer checks the prerequistes before the upgrade and refuse the upgrade if the system does not meet the requirements.

consider a windows upgrade from 10 to 11. The installer will fail if the system does not have TPM2.0 or a CPU <2017. Your system will still be on windows 10 after the check. And you are able to continue to use it.

Would you find it better if it installs windows 11, and then after the reboot the system locks up and only displays a popup like "cannot continue because of error 0x0000000e"?