You must notarize your application to distribute it outside of the Mac App Store. The process verifies your application, ensuring it has a Developer ID code signature and doesn’t contain malicious content. You can notarize your application with Xcode, Xcode command-line tools, or Unity Build AutomationA continuous integration service for Unity projects that automates the process of creating builds on Unity’s servers. More info
See in Glossary.
Unity can create an Xcode project that represents your Unity project during the build process. You can use this Xcode project to notarize your application. Follow the macOS application build steps to create an Xcode project from your Unity project. For information on notarizing the Xcode project, refer to Notarizing macOS Software Before Distribution.
Note: Notarization isn’t required to distribute your application through the Mac App Store. The Mac App Store’s upload process includes content validation similar to notarization. Refer to Delivering to the Mac App Store for more information.
If you can’t notarize your application in the Xcode environment or want to control notarization manually, you can use Xcode’s command-line tools.
To do this, you need the following:
Apple requires that you compress your application before you upload it for notarization. To do this, use the following steps:
Open Terminal and navigate to the directory the application is in.
"application_name.app"
is your built application."application_name.zip"
is the name of the compressed file to generate.ditto -c -k
--sequesterRsrc
--keepParent "application_name.app" "application_name.zip"
This compresses your application and outputs the compressed file to the same directory as your application.
To notarize an application, Apple requires a unique password in a particular format. For information on how to generate an application password, refer to How to generate an app-specific password. The password you generate uses the following format: xxxx-xxxx-xxxx-xxxx
.
If you are using Xcode 13 or later, use Apple’s notarytool to upload and notarize your application. For more information, refer to Customizing the Notarization Workflow and Enable notarization on an older version of macOS.
Note: As of November 1st 2023, Apple have deprecated the use of altool for notarization. You must update your workflow to use notarytool to notarize your macOS applications. For more information, refer to Migrating to the latest notarization tool.
After notarizing your application, any device that runs it can verify that it has a code signature and has no malicious content. However, the device can only perform this verification online. To let a device verify your application without an internet connection, you must staple the application. For information about stapling, refer to Staple the Ticket to Your Distribution.
To staple your application,
"ApplicationName.app"
is the name of your application:xcrun stapler staple "ApplicationName.app"
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
More information
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising. Some 3rd party video providers do not allow video views without targeting cookies. If you are experiencing difficulty viewing a video, you will need to set your cookie preferences for targeting to yes if you wish to view videos from these providers. Unity does not control this.
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.