Search Issue Tracker
By Design
Votes
0
Found in
5.6.2f1
Issue ID
930847
Regression
No
[Gradle] CommandInvokationFailure: Gradle build failed with with non-zero exit value 1
Steps to reproduce:
1) Download attached project 'ExportGradleFailure.zip' and open in Unity
2) Make sure BuildSystem is set to Gradle(new)
3) Connect any android device to your machine
4) Build and Run project on a device
Build will fail with CommandInvokationFailure
Expected result: Using Gradle Build System should build this project without any failure
Actual result: Build fails with exceptions(check attached error message 'GradleBuildFail.txt')
Reproduced with:
5.6.0b1, 5.6.2p3, 2017.1.0f3, 2017.2.0b3
Using Internal(Default) Build System builds this project without any failure
Note: I wasn't able to start building with 5.5.x due to errors in the Console window
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Inconsistent behaviour when interacting with different dropdown types with pointer events on parent Visual Element
- Hidden GameObjects won't re-enable when they have call "DontDestroyOnLoad" function
- Overlay Canvas are rendered on each split-screen camera when HDR is enabled
- [Android] The Player loses focus when using UnityEngine.Handheld.StartActivityIndicator() with Facebook SDK
- Build fails with "Building Library/Bee/artifacts/MacStandalonePlayerBuildProgram/gahcy/hj9mx3z/951.0 failed with output:..." errors when Scripting Backend is set to IL2CPP
Add comment