Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Legacy version for macOS cannot be installed #6277

Closed
4 of 8 tasks
fuzzykiller opened this issue Dec 10, 2023 · 1 comment
Closed
4 of 8 tasks

[Bug]: Legacy version for macOS cannot be installed #6277

fuzzykiller opened this issue Dec 10, 2023 · 1 comment

Comments

@fuzzykiller
Copy link

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

Bug description

When trying to install the macOS client legacy version, an error appears:

“Nextcloud-2.6.5.20200710-legacy.pkg” can’t be opened because Apple cannot check it for malicious software.

This is apparently caused by the notarization info on this file is too old or something. I’m not a macOS developer, sorry if the terms are inaccurate.

# spctl -a -vvv -t install Nextcloud-2.6.5.20200710-legacy.pkg 
Nextcloud-2.6.5.20200710-legacy.pkg: rejected
source=Unnotarized Developer ID
origin=Developer ID Installer: Nextcloud GmbH (NKUJUXUJ3B)

Steps to reproduce

Download legacy client from Nextcloud homepage, attempt to open the .pkg file.

Expected behavior

Client should install.

Which files are affected by this bug

n/a

Operating system

Mac OS

Which version of the operating system you are running.

11.7.9 (20G1426)

Package

Other

Nextcloud Server version

latest aio

Nextcloud Desktop Client version

2.6.5

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

@joshtrichards
Copy link
Member

See #6179 step 2 in the reproduction steps for how to address that.

There's only so much that can be done about legacy clients which aren't even officially supported...

@joshtrichards joshtrichards closed this as not planned Won't fix, can't repro, duplicate, stale Dec 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants