Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3
2019.3.0f5
2020.1
Issue ID
1212189
Regression
No
[IL2CPP] Standalone throws ExecutionEngineException when using generics (interface/struct) with MemoryRfReader
How to reproduce:
1. Open attached project with ILL2CPP Editor "ExecutionEngineException.zip"
2. Make sure that Api Compatibility Level is set to .NET 4.x (Edit -> Project Settings -> Player -> Api Compatibility Level)
3. Enable Development Build (File -> Build Settings -> Development Build)
4. Build and Run
5. Observe Standalone Console
Expected result: no errors are thrown, Standalone console window is not visible
Actual result: "'Realmforge.Evil.Serializers.TypeSerializer::Deserialize<Realmforge.Shared.MemoryRfReader>' for which no ahead of time (AOT) code was generated." is thrown
Reproducible with: 2019.3.0f5, 2020.1.0a20
Could not test with: 2017.4 (ILL2CPP was not yet released), 2018.4, 2019.2 ('UnsafeUtility' does not contain a definition for 'MemSet' error is thrown)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0a24
Resolution Note (fix version 2019.3):
Fixed in: 2019.3.7f1