Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.4
2020.2
2020.2.7f1
2021.1
2021.2
Issue ID
1319683
Regression
No
[Mobile] Crash with no stacktrace when apk is ran
Reproduction steps:
1. Open user's attached project
2. Build and run on Android/iOS
Reproducible with: 2018.4.32f1, 2019.4.23f1, 2020.2.7f1, 2021.1.0b10, 2021.2.0a7
Reproducible with:
VLNQA00030, Lge LG G2, Android: 4.4.2, CPU: Snapdragon 800 MSM8974, GPU: Adreno (TM) 330
VLNQA00277, Asus ROG Phone, Android: 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00006, Samsung Galaxy S7, Android: 8.0.0, CPU: Exynos 8 Octa 8890, GPU: Mali-T880
VLNQA00121, Samsung Galaxy S9, Android: 9, CPU: Exynos 9 Series 9810, GPU: Mali-G72
iPad Pro 12.9 1st gen (iOS 13.4.1)
Not reproducible with:
Editor and Player on Windows
Notes:
- No stacktrace generated
- Resetting packages did not help
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2021.2.X):
The game doesn't crash, it quits itself.
Open MenuManager.cs and read the code. 2 seconds and it calls Application.Quit().