Skip to content

docs(mac): mention hardened runtime in ad-hoc vs no signing section #9647

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.

Sign up for GitHub

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

Merged
mmaietta merged 1 commit into from
Apr 8, 2026
Merged

docs(mac): mention hardened runtime in ad-hoc vs no signing section #9647

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions pages/code-signing-mac.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,13 @@ To disable Code Signing when building for macOS leave all the above vars unset e

Another way — set `mac.identity` to `null`. You can pass additional configuration using CLI as well: `-c.mac.identity=null`. If you are building for ARM, you likely actually want to use ad-hoc signing, in which case you should set `mac.identity` to `-`.

!!! warning "Disabling code signing disables hardened runtime"
Unlike ad-hoc signing (`mac.identity=-`), a complete lack of signing (`mac.identity=null`) will disable hardened runtime in the final output even if its associated configuration setting is enabled. If your goal in setting `mac.identity=null` is to work around one of these issues, consider trying these suggested solutions instead:

* An error saying "[App] cannot be opened because of a problem" and/or a crash report for your app in Console.app containing the text `[framework] not valid for use in process: mapping process and mapped file (non-platform) have different Team IDs)`: make sure the [`com.apple.security.cs.disable-library-validation` entitlement](https://developer.apple.com/documentation/BundleResources/Entitlements/com.apple.security.cs.disable-library-validation) is being applied, which is required when using hardened runtime in an app with ad-hoc signing that loads a framework.
* A crash in Electron Framework: make sure the [`com.apple.security.cs.allow-jit` entitlement](https://developer.apple.com/documentation/BundleResources/Entitlements/com.apple.security.cs.allow-jit) is being applied, which Electron requires.
* Issues when accessing sensors like the camera or microphone or sensitive data on disk such as the Photos library: make sure the [appropriate entitlement](https://developer.apple.com/documentation/Security/hardened-runtime#Resource-Access) is being applied.

## Code Signing and Notarization Tutorial
Thank you to a community member for putting this together.

Expand Down
Loading