Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Cloud build failures with Unity 2017.1

Discussion in 'Unity Build Automation' started by liortal, Sep 18, 2017.

  1. liortal

    liortal

    Joined:
    Oct 17, 2012
    Posts:
    3,562
    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 ?
     
  2. dannyd

    dannyd

    Unity Technologies

    Joined:
    Jun 3, 2014
    Posts:
    785
  3. liortal

    liortal

    Joined:
    Oct 17, 2012
    Posts:
    3,562
    I am using 2017.1.1, i will have a look at the patch releases
     
  4. liortal

    liortal

    Joined:
    Oct 17, 2012
    Posts:
    3,562
    can't find any fix listed for this under patch releases...
     
  5. dannyd

    dannyd

    Unity Technologies

    Joined:
    Jun 3, 2014
    Posts:
    785
  6. liortal

    liortal

    Joined:
    Oct 17, 2012
    Posts:
    3,562
    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.
     
  7. ollieblanks

    ollieblanks

    Unity Technologies

    Joined:
    Aug 21, 2017
    Posts:
    459
    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!
     
    ilmario and liortal like this.
  8. liortal

    liortal

    Joined:
    Oct 17, 2012
    Posts:
    3,562
    @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 ?
     
  9. liortal

    liortal

    Joined:
    Oct 17, 2012
    Posts:
    3,562
    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.
     
  10. liortal

    liortal

    Joined:
    Oct 17, 2012
    Posts:
    3,562
    @dannyd is there any option to allow us (users of UCB) to select the version of android tools to use when building?
     
  11. dannyd

    dannyd

    Unity Technologies

    Joined:
    Jun 3, 2014
    Posts:
    785
    Not currently planned. You could try requesting a specific buildToolsVersion in your gradle template (although I haven't tested this).
     
  12. liortal

    liortal

    Joined:
    Oct 17, 2012
    Posts:
    3,562
    does the cloud VM have different tools versions installed locally ? or only the latest one ?
     
  13. dannyd

    dannyd

    Unity Technologies

    Joined:
    Jun 3, 2014
    Posts:
    785
    Should have the build tools installed back at least a few major versions.