Search Issue Tracker
Active
Fix In Review for 6000.4.0b5
Under Consideration for 6000.5.X
Fixed in 6000.5.0a5
Votes
1
Found in
6000.4.0a1
6000.5.0a5
Issue ID
UUM-125131
Regression
Yes
Editor is not able to load when using NuGet DLL plugins and scripting define symbol DISABLE_TYPEMANAGER_ILPP
How to reproduce:
1. Open the attached project “Sept04.zip“
2. Observe the result
Expected result: The Editor launches
Actual result: Unity loader gets stuck on “Compilling Scripts: Postprocessing IL for Assembly-CSharp”
Reproducible with: 1.4.0-pre.4 (2023.1.0a1, 6000.0.58f1, 6000.2.5f1, 6000.3.0b2)
Not reproducible with: 1.4.0-pre.3 (6000.2.5f1, 6000.3.0b2)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- The problem is specifically with 1.4.0-pre.4 and NuGet DLL files.
- Taking out the NuGet folder out of the project fixes the issue.
Comments (1)
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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
alleriumlabs
Jan 11, 2026 12:33
I'm also experiencing the issue:
Unity 6000.3.3f1
Entities 1.4.3 & 1.4.4
Note that it occurs whether I have InputAction or InputActionMap in a managed component.
I don't have that scripting define set.
The only folder in my project related to NuGet is in /Library/PackageCache/com.unity.nuget.mono-cecil