Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.4
2020.3
2021.1
2021.1.9f1
2021.2
Issue ID
1339876
Regression
No
[ANDROID] Crash caused by Signal 6 when running Unity as an exported project
Reproduction steps:
1) Create a new Unity project
2) Switch platform to Android
3) Export the project and import it to Android Studio
4) Build it and launch on the device. It should start normally.
5) Open UnityPlayerActivity.java and change this line: 'mUnityPlayer = new UnityPlayer(this, this);' into 'mUnityPlayer = new UnityPlayer(getApplicationContext(), this);'
6) Build the project now and try to launch it on the device
Expected result: The application runs successfully
Actual result: The application crashes or freezes on a black screen
Reproducible with: 2018.4.36f1, 2019.4.28f1, 2020.3.12f1, 2021.1.11f1. 2021.2.0a20
Reproducible with:
VLNQA00277, Asus ROG Phone, Android: 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00030, Lge LG G2, Android: 4.4.2, CPU: Snapdragon 800 MSM8974, GPU: Adreno (TM) 330
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
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 window has a dropdown button that throws “MissingReferenceException” error on a new project when the previous project had a GameObject with an animation
- Animator State name overflows outside the visual box when the State has a long name
- UI Document file remains marked as Dirty after Undoing made changes
- Switching between UI Documents with different Canvas sizes marks the UXML file as dirty
- m_Modifications block serializes incorrectly when replacing source prefabs
Resolution Note (2022.1.X):
Non-Activity contexts are not supported for now. We never had a proper support for such use cases.