Search Issue Tracker
Fixed in 0.2.0-preview.1
Votes
0
Found in [Package]
0.1.0-preview.6
Issue ID
1238445
Regression
Yes
"The TypeManager must be initialized" error thrown when the project is built
How to reproduce:
1. Open attached "TypeManagerError-master" project
2. Open Build Settings (File->Build Settings...)
3. Check Development Build option in Build Settings
4. Press Build and Run
Expected result: No errors are thrown
Actual result: The TypeManager must be initialized before the TypeManager can be used error is thrown in the developer's console
Reproducible with: 0.9.0-preview.6, 0.9.1-preview.15 (2019.3.0f1, 2019.3.13f1, 2020.1.0b8, 2020.2.0a11)
Not reproducible with: 0.8.0-preview.8 (2018.4.22f1, 2019.3.13f1, 2020.1.0b8, 2020.2.0a11)
Could not test with: 0.10.0-preview.6 because of namespace errors from NetCode package
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
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
- Frame Debugger Target Selection Search Results window becomes too tiny to even see the default “Editor” selection when there are no search results
- Element name field has no character limit in UI Builder
- Async method in Play Mode being aborted when calling `new System.Windows.Forms.Form`
Resolution Note (fix version 0.2.0-preview.1):
Fixed in Unity Netcode package version 0.2.0-preview.5