Search Unity

Android build fails after upgrading to 2018.3

Discussion in 'Unity Cloud Build' started by dmtroy, Dec 23, 2018.

  1. dmtroy

    dmtroy

    Joined:
    Dec 6, 2014
    Posts:
    6
    After upgrading to 2018.3 for some reason my cloud build now fails for android.
    Here's what looks like the relevant errors


    104: [Unity] at UnityEditor.Android.Command.WaitForProgramToRun (UnityEditor.Utils.Program p, UnityEditor.Android.WaitingForProcessToExit waitingForProcessToExit, System.String errorMsg) [0x00000] in <filename unknown>:0
    105: [Unity] at UnityEditor.Android.Command.Run (System.Diagnostics.ProcessStartInfo psi, UnityEditor.Android.WaitingForProcessToExit waitingForProcessToExit, System.String errorMsg) [0x00000] in <filename unknown>:0
    106: [Unity] at UnityEditor.Android.Command.Run (System.String command, System.String args, System.String workingdir, UnityEditor.Android.WaitingForProcessToExit waitingForProcessToExit, System.String errorMsg) [0x00000] in <filename unknown>:0
    107: [Unity] at UnityEditor.Android.AndroidJavaTools.RunJava (System.String args, System.String workingdir, System.Action`1 progress, System.String error) [0x00000] in <filename unknown>:0
    113: [Unity] Player export failed. Reason: CommandInvokationFailure: Gradle build failed.



    It looks like an issue with gradle but using gradle to build locally still seems to work and the WebGL build still works correctly. I've tried doing a clean build but I've still had no luck.
     

    Attached Files:

  2. dmtroy

    dmtroy

    Joined:
    Dec 6, 2014
    Posts:
    6
    I've resolved the issue, a custom gradle template had been added a while back to work around java issue, for some reason this caused it to fail in the 2018.3 cloud build but not 2018.2 cloud or local build, since the underlying java issue has been resolved I was able to remove the template entirely and it now appears to work