Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.1.X, 2021.2.X
Votes
0
Found in
2019.4
2020.1.17f1
2020.2
2021.1.8f1
2021.2.0a15
Issue ID
1300479
Regression
Yes
Certain errors do not open in Code Editors when double clicking error
Reproduction steps:
1. Open the attached project "NullErrorTest"
2. Open Assets\Scenes\SampleScene
3. Press Play
4. Double click the NullReferenceException in the Console
Expected result: The line causing the error is opened in a Code Editor
Actual result: Nothing happens
Reproducible with: 2019.3.0a8, 2019.4.19f1, 2020.2.2f1, 2021.1.0b4, 2021.1.8f1, 2021.2.0a2, 2021.2.0a15, 2021.2.0a18
Not reproducible with: 2018.4.31f1, 2019.3.0a7, 2021.1.2f1, 2021.1.7f1, 2021.2.0a3, 2021.2.0a14
Notes:
Setting a value to a Null GameObject opens the Code Editor when double-clicking error
GetCompononet<>() on a Null GameObject does not open the Code Editor when double-clicking error
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
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a1
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0b8
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.18f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.18f1