Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
6
Found in
2019.3.0f1
2019.3.0f3
Issue ID
1204992
Regression
Yes
[Android] Application crashes on start when Minify is set to Proguard in the player settings
To reproduce:
1. Create a new project
2. Change the platform to Android
3. Set Minify with Proguard
4. Build and run to android device
Actual result: Application crashes instantly on the device
Expected result: Application should not crash
Not reproduced with: 2017.4.35f1; 2018.4.15f1; 2019.2.17f1; 2019.3.0b12
Reproduced in: 2019.3.0f1; 2020.1.0a18
Tested and reproduced with:
VLNQA00285, Samsung Galaxy J4 Core (SM-J410F), Android 8.1.0, CPU: NOT FOUND, GPU: Adreno (TM) 308
VLNQA00290, Samsung Galaxy S10 5G (SM-G977U), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00099, Google Pixel XL (Pixel XL), Android 9, CPU: Snapdragon 821 MSM8996 Pro, GPU: Adreno (TM) 530
VLNQA00121, Samsung Galaxy S9 (SM-G960F), Android 9, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00110, Samsung Galaxy Note2 (GT-N7100), Android 4.4.2, CPU: Exynos 4 Quad 4412, GPU: Mali-400 MP
Note: logcat attached
Reproduced with mono and IL2CPP
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
- Animator with nested avatar root show missing properties in the Animation Window
- System.Threading.Task tasks cause stall when used in WebGL
- [Package Manager] Access denied when installing some packages
- SerializedProperty.DataEquals returns true for two strings that are different
- Prefab is glitchy when editing in Prefab Mode in a custom UI Environment
SDX_2012
Apr 23, 2020 09:50
Tried LEVENTP comment and did the trick! Thanks!
LeventP
Apr 23, 2020 09:25
If you're using proguard, try adding this line to your proguard file
-keep class com.google.androidgamesdk.* { *; }
welerson_unity
Mar 27, 2020 15:16
The issue keeps on 2019.2.17f1 for me.
TastyCake101
Feb 03, 2020 01:18
Nvm, I just screwed something up.
TastyCake101
Feb 02, 2020 20:25
I'm still experiencing this issue on 2019.3.0f5