When notarizing Mac OSX builds in Unity Build Automation, a common failure occurs with the error "The binary is not signed with a valid Developer ID certificate," despite valid local signing credentials. This often results from exporting the .p12 file without the intermediary certificate. To resolve, export the private key, certificate, and intermediary certificate together from Keychain Access, update credentials with this .p12, and retry the build. Contact support if issues persist.
Issue:
- When setting Unity Build Automation to notarize my Mac OSX builds, my build is failing.
- I've properly entered my signing credentials for Mac OSX signing/notarization, however, Mac OSX builds are failing on the notarization step.
-
In my build logs, I see that there is a warning similar to this:
Followed by an error message:
[warning] Warning: unable to build chain to self-signed root for signer "Developer ID Application: Peter Davidson (6R6AR2S484)"
"message": "The binary is not signed with a valid Developer ID certificate."
Environment:
In Unity Build Automation (UBA), I am attempting to build for Mac OS and have my build artifact signed and notarized for distribution using my uploaded credentials. My credentials are complete and work as expected when I build and notarize the app locally.
Cause:
While there are many potential causes for notarization failure, one of the most common causes is issues with the exported credentials being used to sign and notarize the app. First, please make sure the certificate is valid by validating it in Keychain Access.
Resolution:
If the certificate is valid and you can sign and notarize your app locally with the same credentials, the issue may be that the .p12 needs to be exported along with the intermediary certificate used.
To do this, select the private key, certificate, and intermediary certificate used in Keychain access and right-click to export the .p12 file.
Update or create a new set of signing credentials with this new .p12, and try to build and sign/notarize your OSX app again.
If the issue persists, please contact the Service Support team for further investigation and assistance.