Search Issue Tracker
Won't Fix
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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.