Search Issue Tracker
By Design
Votes
0
Found in
2019.2
2019.3
2019.3.7f1
Issue ID
1232022
Regression
No
Android crash when turning Android Minify to Proguard
Steps to reproduce:
1. Open User-supplied project with Android platform
2. In Project Settings -> Player -> Publishing Settings -> Minify set the Release and Debug to Proguard
3. Build and Run on Android
Expected: The app runs
Actual: The app crashes
Reproduced in: 2019.2.21f1, 2019.3.9f1
Not reproduced in: 2018.4.21f1(Can't build due to errors), 2020.1.0b5 (Can't build due to errors), 2020.2.0a7 (Can't build due to errors)
Note:
Android logs attached in log.txt
Tested with:
VLNQA00277, Asus ROG Phone (ASUS_Z01QD), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00121, Samsung Galaxy S9 (SM-G960F), Android 9, CPU: Exynos 9 Series 9810, GPU: Mali-G72
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
When Proguard is used, it's rules has to be setup correctly, so that required classes/methods are not removed/renamed. There is a Player Setting to setup custom Proguard file. See Proguard documentation on how to write rules.