desktop: macos app signed with invalid signature - `“Zen Browser.app” is damaged and can’t be opened. You should move it to the Trash.`

What happened?

yes, there are other issues. none of them are open, so your users who dont want to search closed issues wont find them. (and really, most of your users wont go from the main marketing website to the source, then eventually find the right one-out-of-12 repos to read the issues on. they’ll just move on.)

“Zen Browser.app” is damaged and can’t be opened. You should move it to the Trash.

This is caused by the development team, apparently, based on other comments, choosing to not just ignore, but intentionally break the MacOS Gatekeeper system.

The dev team have chosen to sign it incorrectly, instead of leaving it unsigned.

that means users dont even have the option to use it unsigned. they’d have to manually bypass gatekeeper entirely.

that is NOT a valid fix, and NOT a valid solution.

if the team dont want to support MacOS, then remove the download link. This literally works for NO ONE now. It’s not some edge case. NO ONE can use this.

If you want to support MacOS either sign it properly (which is really the only answer if you intend this to actually be useful) or dont sign it (which will, eventually, stop being a usable path).

image

Reproducible?

  • I have checked that this issue cannot be reproduced on Mozilla Firefox.

Version

1.0.0-a.28

Severity impact

Critical

What platform are you seeing the problem on?

macOS - aarch64

Relevant log output

No response

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 1
  • Comments: 15 (2 by maintainers)

Most upvoted comments

Apple license is bought should be fixed in next 2-3 days.

Its fixed, but apple gives me the license in 2 days

that’s not what “fixed” means. “fixed” means your users can get access to the fix…that means your published artifacts have been updated, so it’s gone all the way through your release cycle.

I really dont understand closing-before-its-fixed.

why not close it AFTER it’s fixed? (at least, pick one and do that.)

Its fixed, but apple gives me the license in 2 days

that’s not what “fixed” means. “fixed” means your users can get access to the fix…that means your published artifacts have been updated, so it’s gone all the way through your release cycle.

guide on how to deal with it is pinned issue so there is no reason to have multiple same things

but the presence of a guide doesn’t change the fact that the issue is not yet resolved. Just because you have the fix in mind and are planning to ship it with the next version doesn’t mean the issue is closed yet. It’s closed when you ship the fix.

view does not coincide with the view of the developers

only because the developers refuse to acknowledge there are more use cases possible than that of being a browser developer.

the USERS have stated they cant use the solutions and that it’s not “fixed”.

Its fixed, but apple gives me the license in 2 days