Search Issue Tracker
Fixed in 2021.1.X
Votes
6
Found in
2019.3
2019.3.13f1
2020.2
Issue ID
1246081
Regression
No
Excessive IL2CPP Stripping of [RuntimeInitializeOnLoadMethod] method with [Preserve] causes crash on runtime
How to reproduce:
1. Open the attached "UWP_StrippingExcessive.zip" project
2. Make sure that "Script changes while playing" has "Stop Playing and Recompile" option chosen in Preferences Settings
3. Build to UWP
4. Open the Visual Studio Solution file, located in the built project's directory
5. Build the Solution on Local Machine with Debug and x64 options
Expected results: The build does not crash when doing excessive IL2CPP stripping of [RuntimeInitializeOnLoadMethod] method with [Preserve]
Actual results: The build crashes when doing excessive IL2CPP stripping of [RuntimeInitializeOnLoadMethod] method with [Preserve]
Reproducible with: 2019.3.14f1, 2019.1.0b9, 2020.2.0a11
Notes:
- Could not reproduce on 2018.4, because of errors
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
Resolution Note (fix version 2021.1):
Fixed in: 2021.2.0a12