Search Issue Tracker
By Design
Votes
0
Found in
2020.2.6f1
2020.3
Issue ID
1318036
Regression
No
ILPostProcessor causes DLL's that link to UnityEngine.UI.dll to fail and be unloaded on import
How to reproduce:
1. Open attached project "1TestMirror.zip"
2. Right click the TestScript in the project
3. Select Reimport
Expected result: No errors and TestLib.dll is not unloaded
Actual result: Errors appear in the console and TestLib.dll be unloaded from the project
Reproducible with - 2020.3.9f1
Could not test (ILPostProcessor errors) - 2018.4, 2019.4, 2021.1, 2021.2
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
- [VFX] Custom HLSL with 'int' parameter, without the 'in/out/inout' access modifier is not supported
- [Windows] Lens Flare doesn't work in the Lens Flare Showroom URP Sample Scene
- Crash on ujob_execute_job while using OverlapBoxCommand when collisions are more than maxHits
- The validity of the multiple handles can behave differently based on the load/release operations order, when multiple Addressables.LoadAssetAsync and Addressables.Release are used to load and release the same Addressable Asset
- Dynamic text is rendered in the background when it is inside the <font> tag
Resolution Note:
Since 2019.2 UnityEngine UI module is shipped as a package built for .net standard. The built-in DLL we shipped before was built for .net framework 4.0. That means that they use a different base class library and are not binary compatible.
Any library built referencing the old dll must be rebuild referencing the new one or it will fail to run properly.
It has nothing to do with IL PostProcessing as removing all packages doing IL Post Processing still trigger the error.