Search Issue Tracker
Duplicate
Votes
1
Found in
2018.2.0b2
Issue ID
1030607
Regression
No
[iOS][.NET4.6] Exception in System.Reflection.MonoProperty::StaticGetterAdapterFrame when accessing properties using Reflection
To reproduce:
1. Open project
2. Make sure that Scripting runtime is set to .NET 4.6
3. Build and run on iOS device
Expected: project will run without any errors
Actual: exception is thrown:
ExecutionEngineException: Attempting to call method 'System.Reflection.MonoProperty::StaticGetterAdapterFrame' for which no ahead of time (AOT) code was generated.
at System.Reflection.MonoProperty+GetterAdapter.Invoke (System.Object _this) [0x00000] in <00000000000000000000000000000000>:0
at System.Reflection.MonoProperty.GetValue (System.Object obj, System.Object[] index) [0x00000] in <00000000000000000000000000000000>:0
at Repro.Start () [0x00000] in <00000000000000000000000000000000>:0
Rethrow as TargetInvocationException: Exception has been thrown by the target of an invocation.
at System.Reflection.MonoProperty.GetValue (System.Object obj, System.Object[] index) [0x00000] in <00000000000000000000000000000000>:0
at Repro.Start () [0x00000] in <00000000000000000000000000000000>:0
Reproduced: 2017.1.3p4, 2017.2.2p4, 2017.3.2f1, 2017.4.3f1, 2018.1.0f2, 2018.2.0b3
Note: works properly when using .NET 3.5
-
EdwinLyons
May 11, 2018 11:53
I reported this issue initially - I've been informed by Unity that it's a duplicate of https://issuetracker.unity3d.com/issues/uwp-executionengineexception-is-thrown-on-system-dot-reflection-dot-monoproperty-getteradapterframe and that it'll be fixed in a 2018.1 patch release.
-
Gigaflops2017
May 10, 2018 06:51
Same thing.
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
This is a duplicate of issue #1030427