Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.2.0b10
2023.1.0a15
Issue ID
UUM-17163
Regression
Yes
"System.Reflection.TargetInvocationException" is thrown when "Opsive.Shared.Editor.UIElements.dll" is included in the project
How to reproduce:
Open the attached project "My project (1).zip"
Expected results: No errors thrown in the Console window
Actual results: "System.Reflection.TargetInvocationException" is thrown in the Console window
Reproducible with: 2022.2.0a4, 2022.2.0b10, 2023.1.0a15
Not reproducible with: 2020.3.41f1, 2021.3.12f1, 2022.1.20f1, 2022.2.0a3
Reproducible on: Windows 10
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
- Colliders of GameObject with Rigidbody component fail to collide with another GameObject when Rigidbody becomes Kinematic
- Shader cache uploads occur when the "Upload" parameter is disabled in the Cache Server settings
- "ApplySingleProperty clear overrides error" error when applying SerializedReference override to Prefab's nested Prefab
- About Unity window shows extended version numbers including staging tag
- Mono release JIT incorrectly replaces long multiplication with a left-shift operation
Resolution Note:
When referencing individual DLLs from Unity modules, there is a risk that precompiled code gets broken when types are moved from a module to another.
Referencing "monolithic" Unity DLLs which contain all the types allows you to be protected from that kind of issue. These DLLs are located in the Unity installation folder (Managed/UnityEngine.dll and Managed/UnityEditor.dll).