Documentation

Development

User Acquisition

Monetization

Industry

Build Automation

DevOps

Build Automation REST API

Build Automation Editor Package

Open Unity Dashboard

Build Automation

​
​
Build Automation
  • Overview
  • Get started with Build Automation
  • Build Automation Glossary
  • Build configuration
  • Advanced build configuration
  • Run builds
  • Build results
    • Check build results
    • Troubleshooting Build Automation failures
      • Troubleshoot common issues
      • Builds fail immediately
      • Unrecognized project error
      • Clone hangs when you use Git submodules
      • Lightmap baking
      • Android build failures
      • Errors after migration to a new Xcode version
      • macOS notarization failure
      • Problems with iOS Build Automation during XCode export
      • iOS build can't download or install from Unity Build Automation
  • Optimize build speed
  • Manage artifact retention rules
  • Manage concurrent builds
  • Sign build artifacts
  • Build Automation integrations
  • Build Automation API
  • Build Automation Editor Package
  • Reference
  1. Unity Build Automation
  3. Build results
  5. Troubleshoot Build Automation failures

OSX notarization failure

Resolve macOS notarization failures and fix signing issues.
Read time 2 minutes
Last updated 10 months ago

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.
"UBA - Export .p12 file"

UBA - Export .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 Dashboard, open DevOps and select Help & Support > Ticket > File a ticket.
Copyright © 2026 Unity Technologies
LegalPrivacy PolicyCookiesDocumentation Terms of UseDo Not Sell or Share My Personal InformationYour Privacy Choices (Cookie Settings)

"Unity", Unity logos, and other Unity trademarks are trademarks or registered trademarks of Unity Technologies or its affiliates in the U.S and elsewhere (more info here). Other names or brands are trademarks of their respective owners.

Some pages are machine-translated for convenience, and may contain inaccuracies. In the event of conflicting information, the English version is authoritative.

  • On this page

    • Symptoms

    • Environment

    • Potential cause

    • Resolution

Report a problem with this page
​
​