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
- [Windows] Lens Flare doesn't work in the Lens Flare Showroom URP Sample Scene
- Crash on ujob_execute_job while using OverlapBoxCommand when collisions are more than maxHits
- The validity of the multiple handles can behave differently based on the load/release operations order, when multiple Addressables.LoadAssetAsync and Addressables.Release are used to load and release the same Addressable Asset
- OnPointerExit and OnPointerEnter is mistakenly called when an overlapping child Image is destroyed
- Dynamic text is rendered in the background when it is inside the <font> tag
dangvangioi
Apr 08, 2019 03:55
Fixed: You can use System.Diagnostics.Process.GetCurrentProcess().Kill(); replace for Application.Quit().
Try it!
Spierek
Apr 03, 2019 09:16
I'm also getting these in production after building on 2018.3.11f (which according to the post linked below should've included a fix) and it's tanking our vitals rating :/
Any info on whether this fix is going to be properly backported to 2018.3?
https://forum.unity.com/threads/crashes-on-huawei-android-9-devices.632944/#post-4347559
pertz
Apr 02, 2019 16:21
Adding some keywords: this crash occurs when pressing the BACK BUTTON on Android 9, mostly on Samsung devices. Related link/forum post: https://forum.unity.com/threads/crash-with-back-button.605983/
The beginning of the crash log is as follows:
at android.view.ViewGroup.dispatchApplyWindowInsets (ViewGroup.java:7077)
at android.view.ViewRootImpl.dispatchApplyInsets (ViewRootImpl.java:1681)
or
at android.view.ViewGroup.dispatchApplyWindowInsets (ViewGroup.java:7462)
at android.view.ViewRootImpl.dispatchApplyInsets (ViewRootImpl.java:2083)
or
at android.view.ViewGroup.dispatchApplyWindowInsets (ViewGroup.java:7455)
at android.view.ViewRootImpl.dispatchApplyInsets (ViewRootImpl.java:2080)
(depending on the OS version or device)
pertz
Apr 02, 2019 16:17
Im getting hundreds of these crashes in production, there goes down my Android Vitals rating... thanks Unity for only fixing it for 2019.2