This page has instructions and considerations on building your Unity application for macOS.
Before you build an application for macOS, be aware of the chipset differences between Apple devices. Some Apple devices use Intel chipsets and others use Apple silicon. You can use Unity to create both architecture-specific builds and builds that target both Intel and Apple silicon. The available target architectures are:
Architecture | Description |
---|---|
Intel 64-bit | Use Intel 64-bit to build for Apple devices with Intel chipsets. |
Apple silicon | Select Apple silicon to build for Apple devices that use the silicon architecture. |
Intel 64-bit + Apple silicon | Use Intel 64-bit + Apple silicon to generate a macOS build that works on both Intel chipsets and Apple silicon. Note: This results in a build that’s larger than the individual architecture-specific builds, impacting the application size. |
You can set the target architecture for your application from the macOS build settings window.
To build your Unity application:
macOS applications require an information property list file called Info.plist
that has metadata and configuration information for the application. The file holds a list of key-value pairs.
When Unity builds your application, it creates the Info.plist
file. Unity stores this file at ApplicationName.app > Contents > Info.plist. Unity displays required Info.plist
configuration properties in the Player SettingsSettings that let you set various player-specific options for the final game built by Unity. More info
See in Glossary
window that you can set before building the application. These properties are in the Other Settings > Mac App Store Options section.
There are additional keys that you can add to your Info.plist
file. To add them, build the application and use a text editor to edit the file. For information about the available keys, refer to About Info.plist Keys and Values.
macOS applications require entitlements to specify permissions and restrictions that control specific actions of your application. Your application must include entitlements that result in a Hardened Runtime. These entitlements protect your application from code injection, hijacking of dynamically linked libraries, and memory tampering.
To define entitlements, macOS applications use an XML file with the .entitlements
file extension. macOS applications then use a process called code signing to bind the entitlements to an application.
If your application uses plug-insA set of code created outside of Unity that creates functionality in Unity. There are two kinds of plug-ins you can use in Unity: Managed plug-ins (managed .NET assemblies created with tools like Visual Studio) and Native plug-ins (platform-specific native code libraries). More info
See in Glossary
that perform macOS platform-specific actions, you might need to add entitlements to enable those actions. For more information on what actions require entitlements, refer to Apple Developer Entitlements.
Code signing is the process of creating a code signature for an application. This signature guarantees the integrity of applications and safeguards from any tampering. Apple devices use an application’s code signature to detect changes made after the developer created the code signature. If an application doesn’t have a code signature, the device warns the end user before they open the application. Unity automatically code signs any application it builds for macOS.
Notarization is the process Apple uses to check that Developer ID-signed applications don’t contain malicious content. Digital distribution services often require you to notarize your application before you can share it on their platform. The Mac App Store has a content validation system that’s similar to notarization, which means that applications distributed through the store don’t require prior notarization.
Refer to Code sign and notarize your macOS application for more information.
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.