Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2018.1.X
Votes
2
Found in
2018.1.0a7
2018.1.0b10
Issue ID
1013695
Regression
Yes
[Android][IL2CPP] Application.Quit() crashes the app
To reproduce:
1. Download attached project "Unity_ApplicationQuit.zip" and open in Unity
2. Build and run the project on an Android device
3. Wait till APK closes itself
Expected Result: APK closes itself without a crash
Actual Result: APK closes itself alongside with a crash
Notes:
- Logcat is shared in the comments section
- On iOS everything works as expected
- In Editor everything works as expected
- In Standalone (Windows and OSX) everything works as expected
- If you change IL2CPP to Mono, then everything works as expected
Devices:
- Google Pixel 2, OS: 8.1.0, CPU: arm64-v8a, GPU: Adreno (TM) 540
- iPhone 7, iOS 11.0
Reproduced on Unity 2018.1.0a7, 2018.1.0b10 and 2018.1.0b11
Not reproduced on Unity 2017.3.1p4 and 2018.1.0a6
Regression on Unity 2018.1.0a7
Could not check is this fixed because in Unity 2018.2 project becomes corrupted
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
BrunoCroci
Jun 18, 2019 10:17
This issue also happens on 2017.4.27f1.
Device tested: Sony SGP511
Android version: 4.4.2
The usual hack `System.Diagnostics.Process.GetCurrentProcess().Kill();` does not work.
Can we expect a patch to fix that on 2017 LTS?