Search Issue Tracker

Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.




Found in




Issue ID




[iOS] Build fails in Xcode when Cloud Diagnostics are enabled and using another account to build the project

Cloud Diagnostics


Reproduction steps:
1. Create a new project
2. Extract and import contents of "" into your project
3. Enable Cloud Diagnostics for the project (read note 1)
4. Close the Editor completely
5. Build the project using Command Line Argument (IMPORTANT to read note 1):
<UNITY EDITOR PATH> -batchmode -buildTarget iOS -runTests -testplatform playmode -projectpath <PROJECT PATH> -executeMethod CliBuild.MakeiOS -username <LOGIN/E-MAIL> -password <PASSWORD> -quit
6. After the build completes, open the Xcode project located in "build" folder (at the root of the project)
7. Try deploying the project to a device

Expected result: the project successfully deploys or you will have received an error in step 5 indicating that you need to use another account
Actual result: Xcode throws an error message "Please provide an auth token with USYM_UPLOAD_AUTH_TOKEN environment variable", when building in step 5 no indication of something being wrong appears (read note 2)

Reproducible with: 2018.4.26f1, 2019.3.0a1, 2020.2.0a19

1. In step 5 you need to use a different account than the one you used for enabling Unity Services/ Cloud Diagnostics for the project
2. The error message in Xcode is not very informative for the customer (it is possible to make out from keywords such as auth_token, but it should've thrown an error in the building process that more clearly described the problem)
3. This looks similar to Case 1167025 (the difference is that it was not written there that you need a different account)

  1. Resolution Note (2020.2.X):

    Postponing this bug as the team is unavailable to work on it at the moment, but this bug should be addressed in the future.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.