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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note (fix version 0.2.0-preview.1):
Fixed in Unity Netcode package version 0.2.0-preview.5