Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4
2020.1.0a15
Issue ID
1203075
Regression
No
[Mobile] Crash on WillDestroyGameObject() when calling DestroyImmediate() in Start
How to reproduce:
1. Open the attached project for iOS or Android platform
2. Assets > Build AssetBundles
3. Build & Run the project to a device
Actual result: Unity crashes.
Reproducible with: 2017.4.35f1, 2018.4.14f1, 2019.2.15f1, 2019.3.0f2, 2020.1.0a15.
Devices reproducible with:
- iPhone7+ (iOS 11.4.1)
- iPhone 11 (iOS 13.0)
- VLNQA00229 Oneplus OnePlus6T 9 Snapdragon 845 SDM845 Adreno (TM) 630
Notes:
- Not reproducible on Mac Standalone (Both Mono and IL2CPP).
- The issue reproduces only if "Strip Engine Code" is enabled in Player Settings.
- The issue is not reproducible if "Assets/ProductDemo/ResourcesNO" folder is renamed to "Resources".
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
DestroyImmediate should not be used in runtime code, use Destroy instead. See https://docs.unity3d.com/ScriptReference/Object.DestroyImmediate.html