Cloud build failures with Unity 2017.1

We are trying to upgrade to Unity 2017.1; the build (Android) works locally, but in the cloud fails.

I was able to see this exception in the log. Is this a known bug with UCB at the moment ?

I think this should be fixed in latest patch releases of 2017.1. Which version are you building against?

I am using 2017.1.1, i will have a look at the patch releases

can’t find any fix listed for this under patch releases…

It was specific to versions of the Android SDK Tools above 26.0 - I’m assuming you’re on an older version locally? There was also a discussion and some workarounds mentioned here: Sudden error Unable to merge android manifests. - Unity Services - Unity Discussions

The error I am having is not related to manifest merging though. Are you sure its the same thing?

I probably don’t have Android Tools 26.0 locally.

Since Android SDK 26, If any manifest file in your project does not explicitly declare the tools namespace then this occurs.

Check each of your plugins for manifest files and add the below line:
xmlns:tools=“http://schemas.android.com/tools

Hope that helps!

2 Likes

@ollieblanks thanks for the workaround. it’s a bit of a hassle to tell you the truth.

Are there any plans to let me select which Android tools should be used? i believe that most projects are going to be broken by this… what’s the rationale of having it in the cloud build environment ?

Is there any plan to make this work? our project is fairly large, with many 3rd party plugins.
Some of the plugins come as an .aar file. I wouldn’t want to start unpacking all of them to modify their manifests. There should be an easier solution.

One of the main reasons we upgraded to 2017.1 was the ability to build in the cloud (we couldn’t previously, since we couldn’t define a custom Proguard file). Now this issue is preventing us from building in the cloud again.

@dannyd is there any option to allow us (users of UCB) to select the version of android tools to use when building?

Not currently planned. You could try requesting a specific buildToolsVersion in your gradle template (although I haven’t tested this).

does the cloud VM have different tools versions installed locally ? or only the latest one ?

Should have the build tools installed back at least a few major versions.