UCB iOS Builds Faili

Unity Services
1

We are seeing failures on one of our UCB iOS builds that look like UCB is, for some reason, failing to find Unity.

Our other cloud build projects are building fine.

It looks like the issue is only when we specific 2017.3.0p3, and goes away if we just let it select “latest 2017.x”. This is doubly strange as our other cloud build project explicitly uses 2017.3.0p3 on ios and is fine.

51: + Installing UnityCloud build tools
52: /BUILD_PATH/.mason/buildpacks/unity/bin/compile:85:in unity_version_from_exe': Invalid Unity Path (UNITY_EXE). Path name needs to be of the format Unity-X_Y_Z where X_Y_Z is the version number. (RuntimeError) 53: from /BUILD_PATH/.mason/buildpacks/unity/bin/compile:90:in unity_version_at_least?’
54: from /BUILD_PATH/.mason/buildpacks/unity/bin/compile:157:in detect_player_target' 55: from /BUILD_PATH/.mason/buildpacks/unity/bin/compile:578:in ’
56: ! build of ‘default-ios’ failed. compile failed
57: Publishing build 1 of nanu-interactive/colour3d-2018 for target ‘default-ios’…
58: publishing finished successfully.

2

Hi!

I see what you mean. Thanks for bring this to our attention, I’ll make sure the development team knows about it.

Thanks!

3

I believe, to add repro info (as far as you can be sure when fiddling with a cloud service) if I build once with an explicit “latest 2017.x” then switch to 2017.3.0p3 then it works. I can even see the referenced version change in the log output.