Skip to content

macOS releases remain unsigned/unnotarized, causing Gatekeeper prompt after updates #233

Description

@becoolmin

Problem

Issue #66 addressed the broken ad-hoc seal that made macOS releases appear structurally damaged, but the releases are still publisher-unsigned and unnotarized.

On v2.1.11, installing/updating the macOS app still triggers Gatekeeper with:

“Apple could not verify ‘Chat On Steroids’ is free of malware that may harm your Mac or compromise your privacy.”

The current ad-hoc seal provides bundle integrity, but it does not establish publisher trust with macOS. As a result, users may need to bypass Gatekeeper again after replacing the app with a new release.

Question / proposed direction

Would you be open to adding Developer ID signing + Apple notarization to the official macOS release workflow?

If so, I can help prepare the electron-builder / GitHub Actions changes. The maintainer would still need to provide the required Apple Developer certificate and notarization credentials through repository secrets.

Expected outcome

Official macOS release artifacts should:

  • be signed with a Developer ID Application certificate
  • be notarized by Apple
  • pass Gatekeeper without requiring xattr removal or “Open Anyway” after each update
  • retain the existing bundle-integrity checks

Related: #66

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions