Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2017.4.X, 2018.2.X
Votes
72
Found in
2017.3.0b1
Issue ID
969563
Regression
Yes
[Android] Gradle build fails when building project with asset bundle
Reproduction steps:
1. Open the attached project
2. The project has 1 asset bundle. The bug isn't reproducible using other asset bundles or even the same bundle but using different compression
3. Try to build for Android using Gradle
4. Fails with following output:
CommandInvokationFailure: Gradle build failed.
C:/Program Files/Java/jdk1.8.0_111\bin\java.exe -Xmx1024M -classpath "C:\Program Files\Unity 2017.3.0b1\Editor\Data\PlaybackEngines\AndroidPlayer\Tools\gradle\lib\gradle-launcher-4.0.1.jar" org.gradle.launcher.GradleMain "--no-daemon" "assembleDebug"
stderr[
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':packageDebug'.
> Java heap space
and following error window:
https://gyazo.com/6443561e02dd58fc7dff970cd477c218
Regression introduced in 2017.3.0b1
Reproducible in:
2019.1.0a6, 2018.3.0b1, 2018.3.0a6
Environment:
Windows 10 and Mac 10.13
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader Compilation for projects with lots of Shaders can be slow (i.e. VFX Graph asset heavy projects)
- Crash on RebuildTransformHierarchyOrMarkForDestruction when opening a scene
- The Editor hangs when opening a project that uses local packages and Version Control
- Area Light is culled when Camera Frustrum is outside the lights range
- The characters of the bottom option in the Scene View Debug Draw Mode dropdown menu are cut off
RedVonix
Apr 14, 2019 00:04
Also reproduced issue in Unity 2018.3.12f1.
RedVonix
Apr 13, 2019 20:32
Reproduced in 2018.3.8f1.
aureliomv
Jan 31, 2019 00:51
Unity 2018.3.3f1: issue happened with the LWRP asset.
Shows an error "Gradle prewarm failed"
cqc_29a
Jan 23, 2019 23:21
I ran into this bug with Unity version 2018.3.1f1
cqc_29a
Jan 23, 2019 23:19
I ran into this bug with Unity version 2018.3.1f1
cqc_29a
Jan 23, 2019 23:16
I ran into this bug with Unity version 2018.3.1f1
vthera_trond
Dec 12, 2018 00:46
Change logs indicate that this is fixed in 2018.2.16f1. However, we still get fails when running Unity from the command line with -Xmx1024M set when Gradle is called. In 2018.2.5f1, it gave -Xmx2048M. We're not keen to push up to 2018.3 beta, but I'm hoping its fixed there.
vthera_trond
Dec 12, 2018 00:46
Change logs indicate that this is fixed in 2018.2.16f1. However, we still get fails when running Unity from the command line with -Xmx1024M set when Gradle is called. In 2018.2.5f1, it gave -Xmx2048M. We're not keen to push up to 2018.3 beta, but I'm hoping its fixed there.
amaceikaCortina
Dec 06, 2018 16:30
Ran across this issue in 2017.3.1f1 also ran in to build errors with the latest version of Android Studio had to revert the tools folder.
amaceikaCortina
Dec 06, 2018 16:30
Ran across this issue in 2017.3.1f1 also ran in to build errors with the latest version of Android Studio had to revert the tools folder.