The process of building an iOS application with Unity has two main steps:
For further information on how Unity builds iOS applications, refer to How Unity builds iOS applications.
Note: To build an iOS application locally, your development machine must run macOS as Xcode is available only on macOS devices. If you don’t have a macOS device, you can use 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 to build your applications in the cloud.
Before you build your Project for iOS, make sure that you set the Bundle Identifier in the iOS Player SettingsSettings that let you set various player-specific options for the final game built by Unity. More info
See in Glossary (menu: Edit > Project Settings > Player Settings). You can also choose whether your app targets the simulator or an actual device. To do this, change the SDK version field.
To build an Xcode project for iOS, use the following steps:
Tip: After you specify the target directory for the first time, you can use Cmd+B to build and run the application. Unity uses the Append mode to regenerate the Xcode project.
For more information on running an Xcode project in Xcode, refer to Building and running an app(Apple Developer).
If you build a project in a directory that already contains another Xcode project, Unity displays an alert and a choice on how to proceed. There are two options:
Data
and Libraries
subdirectories. It then fills these directories with newly generated Xcode project content. Unity then updates the Xcode project file according to the latest Unity project changes. Unity only supports this mode for the existing Xcode projects generated with the same Unity iOS version. You can store custom built-in code in the classes
subdirectory, as files here aren’t removed.After Unity generates the Xcode project, you can build and run the Xcode project from the command line. To do this, use the following steps:
<device-id>
is your device ID.unity$ xcodebuild test -destination "platform=iOS,id=<device-id>" -scheme Unity-iPhone
When you use command line arguments to specify build settings, they apply to all targets in your Xcode project. To prevent this, some build settings have suffixed versions which you can use to specify which target your build settings affect. You can implement this through User-Defined settings in Xcode > Build Settings. The APP
suffix is used for the application targets and the FRAMEWORK
suffix is used for the framework targets.
When building with xcodebuild, use suffixed versions for the following build settings:
Xcode build setting | Suffixed version |
---|---|
PRODUCT_NAME | PRODUCT_NAME_APP |
PROVISIONING_PROFILE | PROVISIONING_PROFILE_APP |
PROVISIONING_PROFILE_SPECIFIER | PROVISIONING_PROFILE_SPECIFIER_APP |
OTHER_LDFLAGS | OTHER_LDFLAGS_FRAMEWORK |
Based on your custom build pipeline, you can extend the list to cover other settings.
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.