Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.29f1
Issue ID
UUM-44020
Regression
No
“System.Reflection.TargetInvocationException : Exception has been thrown by the target of an invocation” error is thrown when running a deserialization test
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Open the Test Runner Window (Windows > General > Test Runner)
3. Inside the Test Runner Window, select the “Run All Tests” Button
Expected result: All tests pass
Actual result: “DeserializationTestPassOnEditorFailOnIL2CPP” test fails with “System.Reflection.TargetInvocationException : Exception has been thrown by the target of an invocation” error
Reproducible with: 2021.3.29f1, 2022.1.0a14
Not reproducible on: 2022.3.6f1, 2023.1.6f1, 2023.2.0b1
Fixed in: 2022.1.0a15
Reproducible on: Intel macOS 13.4.1
Notes:
- Not reproducible on Mono Scripting Backend or when manually running the “DeserializationTests” test
- The error might be displayed in the Console Window or in the Player
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
This is expected behavior for IL2CPP. In Unity 2022 and later, this behavior is changed, and serialization of these types will work correctly.