Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.2.X, 2019.3.X
Votes
5
Found in
2019.2.0a5
2019.2.1f1
2019.3.0a1
2020.1.0a1
Issue ID
1177292
Regression
Yes
Player Settings window becomes blank and starts spitting errors after going to Android Settings > Icon
How to reproduce:
1. Create a new Project
2. Go to Project Settings > Player > Android Settings > Icon
3. Observe the Project Settings window and Console
Expected Behaviour: The Settings are shown and does not become blank
Actual Behaviour: The Settings window is blank and errors spitting in the Console
Reproducible with: 2019.2.0a5, 2019.2.8f1, 2019.3.0b5, 2020.1.0a7
Not reproducible with: 2017.4.32f1, 2018.4.10f1, 2019.2.0a4
Note: Reproducible only when SDK is not installed
-
ProbePLayer
Dec 01, 2020 16:05
This exact error happened to me on Unity 2019.2.17, after installing a few older SDK platforms via the Android Studio it disappeared.
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
- The Editor becomes unresponsive and memory allocation errors are spammed in the Console when Generating Lightning
- Crash on BatchApplyPropertiesFromSourceAssetDB when opening a specific project
- Scene view Camera cannot be moved with WASD/QE keys when the Right Mouse Button is held down and the Mouse is not moved
- Crash when calling default interface method from virtual method with same name
- [Android] Unity does not include the ".aab" extension for an AppBundle when it is built via script with the buildPlayerOptions.locationPathName = "AppName.apk" and EditorUserBuildSettings.buildAppBundle = true
Resolution Note (fix version 2020.1):
The issue was happening because of wrong JDK pointed. Please make sure to use a correct one (ideally, built-in with Unity). In the meanwhile, Unity will log an exception but still display the settings UI.
Fixed in 2020.1.0a11, backported to 2019.2.18f1, 2019.3.0b10