Search Issue Tracker
Duplicate
Votes
0
Found in
2017.3.1f1
Issue ID
1025568
Regression
No
Android build crashes when using Proguard or Gradle (Experimental) in the Minify settings
To reproduce:
1. Open the project, attached by the user (BustedAndroidBuild.zip)
2. In the Player Settings -> Other Settings Minify section, set Debug to Proguard or Gradle (Experimental)
3. Build and Run project on an Android device
4. Observe that as soon as the build launches on the device, the errors show up and the application closes
Expected: the build works on the device
Reproduced in 2017.3.1f1, 2018.1.0f1
Couldn't test in 2018.2.0b1: the build fails with error "Could not find method implementation() for arguments [{name=MaxUnityPlugin, ext=aar}] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler."
Could not test in earlier versions: the build fails with error "Could not find method google() for arguments [] on repository container"
Tested on Samsung-SM-G950U (Galaxy S8)
The issue occurs in Development Version as well as Release version
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
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
This is a duplicate of issue #1018967