Notarization: The binary is not signed with a valid Developer ID macOS Origin: Platform & cloud Last updated 5 Nov 2026

macOS notarytool: status: Invalid — The binary is not signed with a valid Developer ID certificate / does not have the hardened runtime enabled

Apple's notary service rejected your app; the log lists exactly which binaries failed which checks.

Exact message you may see The binary is not signed with a valid Developer ID certificateThe signature does not include a secure timestampThe executable does not have the hardened runtime enabledstatus: Invalid notarytoolThe signature of the binary is invalid
Seen on: macOS

Meaning

Fetch the log: xcrun notarytool log SUBMISSION_ID --keychain-profile PROFILE. Typical failures: not signed with a Developer ID Application certificate, hardened runtime missing (codesign --options runtime), no secure timestamp (--timestamp), or unsigned nested binaries. Sign inside-out, then xcrun stapler staple.

Common causes

  • Signed with a Development/Apple Distribution certificate
  • Hardened runtime not enabled
  • Missing secure timestamp
  • Unsigned nested frameworks/binaries
  • SDK too old (requirement)

⚡ Quick fix

  1. xcrun notarytool log ID --keychain-profile NAME
  2. Sign with codesign --force --options runtime --timestamp --sign "Developer ID Application: …"
  3. Staple: xcrun stapler staple MyApp.app

Detailed fix by platform

macOS

  1. xcrun notarytool submit app.zip --keychain-profile NAME --wait

How to diagnose

  1. Log — Which issue?
  2. Cert — Developer ID Application?
  3. Runtime — Hardened?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

Apple could not verify "x" is free of malware — macOS: “app” cannot be opened because Apple cannot check it for malicious software / Apple could not verify “app” is free of malware that may harm your Mac (macOS)Apple could not verif…codesign: resource fork, Finder information, or similar detritus not allowed — macOS: Error: resource fork, Finder information, or similar detritus not allowed (macOS)codesign: resource fo…Command CodeSign failed — Command CodeSign failed with a nonzero exit code (errSecInternalComponent / resource fork, Finder information not allowed) (iOS)Command CodeSign fail…doesn't include signing certificate — Provisioning profile "x" doesn't include signing certificate "Apple Development: Name (ID)" (iOS)doesn't include signi…doesn't include the currently selected device — Provisioning profile "x" doesn't include the currently selected device (iOS)doesn't include the c…Failed to register bundle identifier — Failed to register bundle identifier: The app identifier "com.x" cannot be registered to your development team because it is not available (iOS)Failed to register bu…gpg failed to sign — error: gpg failed to sign the data — fatal: failed to write commit object (Git)gpg failed to signHomebrew Cask: It seems there is already an App at — Homebrew: Error: It seems there is already an App at '/Applications/Chrome.app' (macOS)Homebrew Cask: It see…Notarizat…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.