Search Issue Tracker
Third Party Issue
Votes
0
Found in
2019.3.0a1
Issue ID
1387001
Regression
No
[Android] Signal 9 is not returned after Application.Quit() on <9 Android devices
To reproduce:
1. Have a project that utilizes Application.Quit()
1. Build the project and run on applickable device
2. Observe the logcat - Signal 9 is missing
Reproduced on: 2021.2.3f1, 2022.1.0b2
Devices the reproduce the issue:
VLNQA00230 - OnePlus 6T (ONEPLUS A6013), OS: 9.0.0, CPU: Snapdragon 845 SDM845, GPU: Adreno 630
VLNQA00011 - Xiaomi Mi 5s (MI 5s), OS: 6.0.1, CPU: Snapdragon 820 MSM8996, GPU: Adreno 530
VLNQA00010 - Samsung Galaxy S8 USA (SM-G950U), OS: 7.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno 540
Devices that don't reproduce the issue:
VLNQA00341 - Note20 Ultra 5G INT (SM-N986B), OS: 10, CPU: Exynos 990, GPU: Mali-G77
VLNQA00267 - Samsung Galaxy S10+ (SM-G975F), OS: 10.0.0, CPU: Exynos 9 9820, GPU: Mali-G76
VLNQA00377 - Google Pixel 5 (Pixel 5), OS: 12, CPU: Snapdragon 765/765G, GPU: Adreno 620
---------- Xiaomi Mi A2 (Mi A2), OS: 10, CPU: Snapdragon 660, GPU: Adreno (TM) 512
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Resolution Note (2022.2.X):
This is printed (or not) by OS, not Unity, we don't control it.