[Bug]: Update strategy for MacOS Big Sur

[tflidd]

⚠️ Before submitting, please verify the following: ⚠️

• This is a bug, not a question or a configuration issue.
• This issue is not already reported on Github (I've searched it).
• Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• I agree to follow Nextcloud's Code of Conduct

Bug description

I need to state that the server and client are up to date, but putting the client up to date is the current issue.

I am on macOS big sur (11.7.10), and the Nextcloud client is version 3.2.3 and the client says 3.10.1 was available:

But the client there is just for macOS 12+, so for me it would be the legacy version for macOS 10+, but that is version 2.6.5, so much older than the version I already have. And there seems to be an issue as well #6179.

Unfortunately, I have to stick with macOS 11, however it is still a supported version. The Client version 3.2.3 is still running, some report (see the report on the issues on 2.6.5) that even the newer version is working. Why is the version not officially supported, just a lack of testing, problems of features?

Steps to reproduce

1. Use macOS 11.7
2. Use Nextcloud desktop client, until you hit version 3.2.3
3. It recommends to update to 3.10.1, but this version is supposed to support only macOS12+
   ...

Expected behavior

More details, why some version are supported / not supported any more.
Help users with older versions, allow people to use older hardware.

Which files are affected by this bug

nextcloud

Operating system

Mac OS

Which version of the operating system you are running.

macOS 11.7

Package

Other

Nextcloud Server version

26

Nextcloud Desktop Client version

3.2.3

Is this bug present after an update or on a fresh install?

Updated from a minor version (ex. 3.4.2 to 3.4.4)

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

• Default internal user-backend
• LDAP/ Active Directory
• SSO - SAML
• Other

Nextcloud Server logs

No response

Additional info

No response

[marcotrevisan]

Hello, in my opinion the problematic behaviour is that the client is inviting the user to upgrade the package, but then, once upgraded, the package won't work anymore.
It sould be more "fair" and warn the user that the current MacOS version is in end of life for NC Desktop and stop any path to package upgrades.

[marcotrevisan]

In addition, I'd say that stopping support for a major OS version in a bugfix release (3.10.0 -> 3.10.1) is not very usual... I would expect such a change in a new major/feature version... my 2 cents

[philiprenich]

fwiw, the "legacy" version 2.6.5 didn't even work for me on MacOS 11.7.1 - it launches and immediately crashes, leaving only Nextcloud Extensions running in the Activity Monitor, and no toolbar icon.
I think my v3 app had auto updated itself until it no longer worked. Not sure, I wasn't expecting it to be unsupported. Going to look for a download for the v3.2.3 that supposedly works.

[philiprenich]

fwiw, the "legacy" version 2.6.5 didn't even work for me on MacOS 11.7.1 - it launches and immediately crashes, leaving only Nextcloud Extensions running in the Activity Monitor, and no toolbar icon. I think my v3 app had auto updated itself until it no longer worked. Not sure, I wasn't expecting it to be unsupported. Going to look for a download for the v3.2.3 that supposedly works.

3.10.0 worked fine for me. (https://download.nextcloud.com/desktop/releases/Mac/Installer/)

[neonmate]

@mgallien Mac OS version 11.x is the last supported version for e.g. all MBP Late 2013. It still receives security updates (latest was https://support.apple.com/en-us/HT213915) and there is no possibility to update to Mac OS version 12.x.

Can you consider rolling back the changes made in b15369c and continue support for at least version 11.x? I understand that supporting old OS versions is painful. But sticking to an old version of the nextcloud client is only a temporary solution.

[tflidd]

This was the related pull request, but it is not clear why it requires a new MacOS version:
#6174

[marcotrevisan]

Something is going on under the hoods: #6207

[aaszodi]

MacOS Big Sur 11.7 is a solid OS, it is still supported by Apple (gets regular updates). But even if it weren't, a client application has absolutely no right to force the user to upgrade the OS. As others have pointed out before me, the updater must test the current OS version and refuse to install if the new version happens to be incompatible with said OS.

Slightly off-topic but related bug: the MacOS client has an option in "Settings" that seemingly lets the user to turn off the check for updates:

But despite the unchecked checkbox it does check for updates and keeps nagging the user to upgrade.

And while we are at it: I personally see absolutely no reason to install each and every update. Version 3.9 of the MacOS client worked for me without a hitch, just like all versions before it that I can remember (your mileage may vary of course). Yes, I gave in to the nag screen several times ... but not any more, as I am not going to upgrade from Big Sur, thank you very much.

Parting shot: Donald Knuth famously said that "premature optimization is the root of all evil". If I may humbly paraphrase him: "Unnecessary upgrades are the root of all evil". Thank you.

[xbluemonkx]

MacOS Big Sur 11.7 is a solid OS, it is still supported by Apple (gets regular updates).

According my research November 2023 was the last security patch by apple and Big Sur has now officially reached EOL.

[Tegenwind]

Yes, Big Sur is now officially EOL, but seeing as the 3.10.0 update still supported Mojave (10.14), dropping 3 OS releases in a minor update could be considered somewhat drastic..

As for the automatic update check, this has been an issue since about June 2022 if I'm not mistaken.
There's been multiple attempts to fix it, but the behaviour remains the same.

Related issue: #5429