Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.3.X, 2019.1.X
Votes
0
Found in
2019.2.0a7
Issue ID
1135018
Regression
No
[Android] Application.Quit and Application.Unload crashes the app on Android 9.x devices when Scripting backend is set to IL2CPP
How to reproduce:
1. Open the attached project
2. Make sure Scripting Backend is set to IL2CPP
3. Build and run on device
4. Press Quit button
5. Check the logcat
6. If you don't see the crash log reopen the app and repeat
7. Later do the same with Unload
Result: app crashes
Reproducible: 2019.2.0a4, 2019.2.0a7, 2019.1.0b6, 2019.1.0a10, 2018.3.8f1
Fixed in - 2019.2.0a11
Note:
-Crashes on both development and non-development build
-Crashes armv7 and arm64
-Crash doesn't reproduce with Mono
Tested and reproduced:
VLNQA00123 Google Pixel 2 XL (Pixel 2 XL) Adreno (TM) 540 Snapdragon 835 MSM8998 Android 9
Tested and didn't reproduce:
VLNQA00122 Samsung Galaxy S9 (SM-G960F) Mali-G72 Exynos 9 Series 9810 Android8.0.0
VLNQA00155 Meizu PRO 7 Plus (PRO 7 Plus) PowerVR Rogue Marlowe MediaTek Helio X30 Android 7.0
VLNQA00223 Samsung Galaxy S4 (GT-I9505) Adreno (TM) 320 Snapdragon S4 Plus MSM8960 Android 5.0.1
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
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
LostBoyRadPaisley
Dec 22, 2021 22:43
I'm still seeing this issue using unity 2020.3.16f1
ritnickior
Aug 17, 2019 15:46
Will also be fixed in 2017 LTS?
Mese
Aug 14, 2019 08:35
Please! Unity! Fix in 2017.4 LTS!
Specially now that we are forced to use IL2CPP!
BrunoCroci
Jun 18, 2019 10:12
This issue is also happening on 2017 LTS (2017.4.27f1) on a 4.4 Android and `System.Diagnostics.Process.GetCurrentProcess().Kill()` does not work. Can we expect a patch or anything for the 2017 LTS?!
FIFTYTWO
May 31, 2019 14:15
I have tried DANGVANGIOI's workaround with System.Diagnostics.Process.GetCurrentProcess().Kill() as well and got Win32Exception too without closing the app. Need some workaroud because 2019.2 is in beta yet.
charlie_sbg
May 23, 2019 23:41
As a work-around, I tried the System.Diagnostics.Process.GetCurrentProcess().Kill(); fix as mentioned by @DANGVANGIOI.
I'm on 2018.3.0f1
What I get is a strange Win32Exception: Success. If I catch this and eat it, the game keep srunning. I haven't found a way around this. Any ideas?
wowipop
May 18, 2019 05:48
2019.1.3 crash as well
wowipop
May 14, 2019 09:51
2019.1.2 crashing both Application.Quit() and Application.Unload()
MochiBits
Apr 15, 2019 21:39
2018.3.12 yes crashing
2018.3.2 no crashing
Have not tried other versions. Have not tried Dang's fix.
HomegrownGames
Apr 12, 2019 00:05
Any news when this will be properly backported into 2019.3 ?
Issue is still killing the Android vitals for quite some apps in production.