OSX notarization failure#

Symptoms#

• When you set your Unity Build Automation to notarize your macOS builds, your build fails.

• You enter your correct credentials for macOS signing or notarization, but the macOS builds fail at the notarization step.

• In your build logs, there is the following warning: [warning] Warning: unable to build chain to self-signed root for signer "Developer ID Application: Peter Davidson (6R6AR2S484)"

  Followed by an error message:

  "message": "The binary is not signed with a valid Developer ID certificate."

Environment#

In Unity Build Automation (UBA), you want to build for macOS and you've used your uploaded credentials to sign and notarize your build artifact for distribution. Your credentilals are complete and work correctly when you build and notarize the app locally.

Potential cause#

There are many potential causes for notarization failure. One of the most common causes is a problem with the exported credentials that you use to sign and notarize the app.

Resolution#

First, ensure the certificate is valid by validating it in Keychain Access.

If the certificate is valid and you can sign and notarize your app locally with the same credentials, you might need to export the .p12 with the intermediary certificate you use.

To export the .p12, select the private key, certificate, and intermediary certificate used in Keychain access and right-click to export the .p12 file. For more detailed instructions, refer to Creating a p12 file.

Update or create a new set of signing credentials in the target in the Basic settings tab of your build target with this new .p12, and try to build and sign or notarize your OSX app again.

If the issue persists, please contact the Service Support team. To submit a ticket from the Unity Cloud Dashboard, open DevOps and select Help & Support > Ticket > File a ticket.