[Bug]: macOS CheckUpdate Update Error

[intdel]

⚠️ 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

When checking for update on macOS nextcloud client, I am getting an error.

Steps to reproduce

1. Open Settings
2. Check for Updates

Expected behavior

It checks for updates successfully

Which files are affected by this bug

sparkleupdater_mac

Operating system

Mac OS

Which version of the operating system you are running.

14.5

Package

Appimage

Nextcloud Server version

29.0.1

Nextcloud Desktop Client version

3.13.0

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

Fresh desktop client install

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

[jameskimmel]

I have had the same error in 3.13.0 standard.
Installed 3.13.0 VFS and the error persists.

[ghost]

I do also have this problem, what logs are needed to fix it?

[intdel]

Thanks for the quick fix. I can confirm it works.

[martinjgrunwald]

I just updated to 3.14.0 and I am getting this exact error. I already uninstalled, deleted Library files and rebooted but that didn't fix it

[vapaa]

I also have the error with MacOS 14.7 and the Nextcloud desktop client 3.14.0.

[henrygermany]

Had the same Error on MacOS 14.6.1 with Nextcloud Desktop client 3.14.0. Turned out the update channel got switched to daily, after I switched to stable the error does no longer come up.

[vapaa]

that was a good tip, I changed the update channel to "stable" and no longer got an error message. However, after I changed it back to daily, the error message came back. At least with the workaround "set to stable" I no longer get an error message.

[foss-]

As the remaining issue is something different than what was reported in the issue here and which has been fixed, why not report a new issue for the remaining problem?