iOS Batchmode builds fail due to missing USYM_UPLOAD_AUTH_TOKEN env var

Unity Services
, ,
1

Our CI iOS builds started to fail yesterday. Very looks like old issue is back:

2

Hi,

Could you please let us know what Unity version you’re using? Thanks!

3

This also happened to me last night in our CI, It happened a few days ago and it was fixed by using username+pasword, but it started failing againt wednesday night. The unity version we’re using is 2020.3.25

4

Actually for me it got fixed once I logged-in with out CI user to cloud.unity3d.com and accepted some eula

5

If your project is still having this issue, could you open a support ticket? The support team will need to get more information in order to investigate the cause of the issue.

6

Hi,

I also have this issue with our CI builds, because we are using Unity Server License and launching the compilation via batchmode (that’s why we can’t fix it by adding the username + password).

The unity version we are using is 2020.3.13 LTS, compiling it with CI using floating license with Unity Server License.

Is there any way to fix this issue?

Thanks,

7

Hello, it’s now June 2024 and I also have this issue with the entire series of 2022.3.NN releases (currently using 2022.3.34) using a floating license via batchmode. Neither the generated iOS xcode project, other platform builds, or calling UnityEditor.CrashReporting.CrashReporting.GetUsymUploadAuthToken using reflection have token data. (our project has externally built plugins that I’ve automated the upload of debug symbols during build)

Are there any reported fixes or workarounds? as far as I’m aware you can’t just feed a username/serial/password as arguments to the editor which is the workaround for a regular license.