Symptoms:
My game builds fine locally, but it fails in Unity Build Automation.
Cause:
There are several reasons why this could happen, but the most common are:
- Not all required files are checked into your source control
- You are using different versions of the Unity Editor or platform-specific tools (Xcode/Android Tools).
Resolution:
Sometimes, your source control won't have all the files that your local machine has. First, you should check if it builds locally from a fresh checkout by doing the following:
- Clone/check out your project into a new directory from source control.
- Open the Unity project in the same version of the Editor that you are trying to use with Build Automation.
- Build a version of your project for the same platform you are targeting in Build Automation, ideally using batchmode to replicate the process used on the build machines.
- If your project is built using platform-specific tools, ensure those match the same versions you are using on the Build Automation service (Android Tools/Xcode).
- Verify that the errors received in your Build Automation log are not apparent during this local build.
If it still looks fine locally, try doing a clean build from the dashboard (see below):


Be sure to check our forums and the Unity Cloud Service Status page, where we post about current issues that could be affecting your builds.
You can find the list of Xcode versions supported by our team in the Unity Build Automation documentation.