Search Issue Tracker
Won't Fix
Won't Fix in 2020.3.X
Votes
0
Found in
2020.3.44f1
Issue ID
UUM-27838
Regression
No
Error "Null reference exception" is thrown in the build when Managed Stripping Level is set to Low, Medium or High
How to reproduce:
1. Open the project "IN_29919"
2. Press File -> Build Settings
3. Enable the "Development Build"
4. Press "Build And Run"
Expected result: no errors in the Player
Actual result: "NullReferenceException: Object reference not set to an instance of an object" error thrown
Reproducible with: 2020.3.44f1, 2021.1.0a5
Not reproducible with: 2021.3.18f1, 2022.2.6f1, 2023.1.0b3, 2023.2.0a1
Fixed in: 2021.1.0a6
Reproducible on: Windows 10 Pro
Note: Development build chosen only to see errors better
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
We won't be fixing this for 2020.3. Stripping got improved in for 2021 and the error doesn't exist there.
Workaround: Add the parts that you don't want stripped to the link.xml file.
See https://docs.unity3d.com/Manual/unity-linker.html for how that works.
Resolution Note (2020.3.X):
We won't be fixing this for 2020.3. Stripping got improved in for 2021 and the error doesn't exist there.
Workaround: Add the parts that you don't want stripped to the link.xml file.
See https://docs.unity3d.com/Manual/unity-linker.html for how that works.