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

Problems with iOS Build Automation during XCode export

Resolve iOS build automation problems during Xcode export in Unity Build Automation.
Read time 1 minute
Last updated 10 months ago

Symptom

Build errors appear in the Xcode project when you build your iOS project in Unity Build Automation (UBA).

Causes

Most Xcode build failures in UBA are related to third party plug-ins, specifically those that require a minimum version of Xcode or require that you disable bitcode.
Build errors can also occur if the post process can't find the Xcode project and can't add the appropriate libraries.

Resolution

Ensure you can build your project locally in the desired version of Xcode with the same settings: don't modify the Xcode project unless you do the same modifications in the post-export script in UBA.
If the post process can't find the Xcode project, you need to pass that path to 
OnPostProcessBuild
. Some third party plug-ins, or your own code, require a way to modify the XCode project to add libraries or files, which you can use post-process attributes and the Scripting API to do.

Additional resources

There are several Unity Discussions forum posts available, which can help to solve different issues related to iOS projects:
  • Add frameworks via post-process scripts to the XCode project.
  • Add items to info.plist via post process scripts to the XCode project.
  • Add other linker flags for missing libraries in third party tools.
  • Activate iCloud settings.
  • Add security frameworks.
  • XCode frameworks.
You can also refer to the following pages:
  • How to build locally in batchmode.
  • A support article on how to disable bitcode in a Unity Project.
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

    • Symptom

    • Causes

    • Resolution

    • Additional resources

Report a problem with this page