Search Issue Tracker

Not Reproducible



Found in


Issue ID




[Android] Application.Quit and Application.Unload crashes the app on several 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
Result: app crashes, check the logcat, you should see the crash log

5. Reopen the app
Result: if you run arm64, screen will be just black. Armv7 opens app normally

6. Later do the same with Unload

Reproducible: 2019.2.0a4, 2019.2.0a7, 2019.1.0b6, 2019.1.0a10, 2018.3.8f1

-Crashes on both development and non-development build
-Crashes armv7 and arm64
-Crash doesn't reproduce with Mono

Tested and reproduced:
VLNQA00176 Xiaomi Redmi 4 (Redmi 4) Adreno (TM) 505 Snapdragon 430 Android 6.0.1

Tested and didn't reproduce:
VLNQA00123, Google Pixel 2 XL (Pixel 2 XL), Android 9, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540 - crash is different and already reported
VLNQA00122, Samsung Galaxy S9 (SM-G960F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00155, Meizu PRO 7 Plus (PRO 7 Plus), Android 7.0, CPU: MediaTek Helio X30 MT6799, GPU: PowerVR Rogue Marlowe
VLNQA00202, Samsung Galaxy Note9 (SM-N9600), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00025, Xiaomi Mi 5s (MI 5s), Android 6.0.1, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
VLNQA00223, Samsung Galaxy S4 (GT-I9505), Android 5.0.1, CPU: Snapdragon S4 Plus MSM8960, GPU: Adreno (TM) 320
VLNQA00166, Huawei P20 (EML-L29), Android 8.1.0, CPU: HiSilicon Kirin 970, GPU: Mali-G72
VLNQA00139, Vivo Xplay6 (vivo Xplay6), Android 7.1.1, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530

Comments (2)

  1. AAulicinop

    Sep 19, 2019 20:23

    This is happening too with Unity 2019.1.14f1. App crashes when reopening after being closed through Application.Quit().

    OnePlus 6t (ONEPLUS A6013) - OxygenOS 9.0.16, CPU: Snapdragon 845, GPU: Adreno (TM) 630

  2. iabulko

    Sep 09, 2019 09:26

    We actually tested it on many Xiaomi devices and all of them had this issue.

Add comment

Log in to post comment