You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
1.1 macOS notarization for distribution outside the Mac App Store (HARD). Platform Mechanics 2026
#1640
An app distributed with a Developer ID (not through the Mac App Store) must be notarized or Gatekeeper blocks it. The four steps. build with every executable and dylib signed. sign with a Developer ID certificate plus a secure timestamp and the hardened runtime. submit with xcrun notarytool and wait for the ticket. staple with xcrun stapler. A bare executable cannot be notarized. it is wrapped in a ZIP, DMG, or PKG container first.
Hardened runtime is a notarization prerequisite (enable the capability and declare the needed entitlements).
The signing form is codesign --options runtime --timestamp -s "Developer ID Application: NAME (TEAMID)" <App> (the --options runtime flag is the hardened runtime, --timestamp is the secure timestamp).
What breaks. an app that is not stapled fails to launch on an offline Mac, because Gatekeeper cannot fetch the ticket. an app that is not notarized at all shows the "Apple cannot check it for malicious software" or "app is damaged" dialog and is blocked on stricter policies.
This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run bash scripts/install.sh install, then run the guard on your project before you submit. Questions or a correction? Reply below.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
An app distributed with a Developer ID (not through the Mac App Store) must be notarized or Gatekeeper blocks it. The four steps. build with every executable and dylib signed. sign with a Developer ID certificate plus a secure timestamp and the hardened runtime. submit with
xcrun notarytooland wait for the ticket. staple withxcrun stapler. A bare executable cannot be notarized. it is wrapped in a ZIP, DMG, or PKG container first.codesign --options runtime --timestamp -s "Developer ID Application: NAME (TEAMID)" <App>(the--options runtimeflag is the hardened runtime,--timestampis the secure timestamp).xcrun notarytool submit <container> --apple-id ... --team-id TEAMID --password <app-specific-password> --wait, thenxcrun stapler staple <App>.Sources. Apple notarizing macOS software, Apple Developer ID, Apple customizing the notarization workflow.
Source section. PLATFORM-MECHANICS-2026.md, 1.1 macOS notarization for distribution outside the Mac App Store (HARD).
This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run
bash scripts/install.sh install, then run the guard on your project before you submit. Questions or a correction? Reply below.All reactions