Search Issue Tracker
Fixed
Fixed in 2021.3.14f1
Votes
0
Found in
2021.3.13f1
Issue ID
UUM-19061
Regression
No
"NullReferenceException: Object reference not set to an instance of an object" errors become visible when "Maximize" window function is used in "Runner Game" tutorial section
How to reproduce:
1. Create a new project using the "Runner Game" template;
2. Go to "Tutorial" section;
3. Click on meatball menu and select "Maximize";
4. In new maximized view select the same menu and select the same "Maximize" function;
5. Observe "Console" window.
Expected results: Window should be returned to the initial view. No errors should be in console.
Actual results: Console displays errors.
Reproducible with: 2021.3.13f1
Could not test with: 2020.3.41f1, 2022.1.22f1, 2022.2.0b14, 2023.1.0a18 (Template is not available)
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
- Editor crashes when debugging a for loop
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
Resolution Note (fix version 2021.3.14f1):
Issue verified on "Runner Game" version 1.0.2.
Maximize function works correctly.