Search Issue Tracker
Duplicate
Votes
0
Found in
2021.3.10f1
Issue ID
UUM-21606
Regression
Yes
"NullReferenceException" is thrown when the development build is built in previous folder as the regular build
How to reproduce:
1. Open the user’s attached project “Unity-2021.3.5-URP3DCore.zip“
2. Press File → Build
3. Make sure the Development build is disabled
4. Build the project
5. Repeat step 2 and enable the Development build
6. Build the Project in the same folder as the previous build
7. Run the build
8. Observe the build
Expected result: no errors in the build
Actual result: error in the build
Reproducible with: 2021.2.9f1, 2021.3.10f1
Not reproducible with: 2020.3.42, 2021.2.8f1, 2021.3.11f1, 2021.3.14f1, 2022.1.23f1, 2022.2.0b15, 2023.1.0a19
Reproducible on: Windows 10 Pro
Full error: “NullReferenceException: Object reference not set to an instance of an object”
Note: also reproducible on new URP project
Workaround: build Development build in a separate folder
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
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
Resolution Note:
This issue was reproduced in 2021.2.5f1, 2021.2.9f1, 2021.3.10f1 but was fixed in 2021.3.11f1. It also doesn't reproduce on 2022.1, 2022.2 or 2023.1.0a19.
Duplicate of another internal issue: UUM-13827: DebugManager construction error