Search Issue Tracker
Won't Fix
Won't Fix in 6000.0.X
Votes
0
Found in
2021.3.21f1
2022.2.11f1
2023.1.0b8
2023.2.0a6
2023.3.0a3
6000.0.0b11
Issue ID
UUM-31227
Regression
No
NullReferenceException error occurs when a GameObject with a script component referencing its unique ID is selected before or during Play Mode
How to reproduce:
1. Open the “NullReferenceException error“ project
2. Select the “TimerIDTest“ GameObject in the Hierarchy
3. Enter Play Mode
4. Observe the Console Window
Expected result: No errors seen in the Console Window
Actual result: “NullReferenceException“ error seen in the Console Window
Reproducible with: 2021.3.21f1, 2022.2.11f1, 2023.1.0b8, 2023.2.0a6
Could not test with: 2020.3.46f1 (due to errors)
Reproducible on: Windows 10
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Default references only works in EditMode, if they are used in PlayMode they will be null. But Default References have another behavior when in Editor-Only assemblies (ie. /Editor folder when not using Asmdef's, or Asmdefs only compatible with the Editor).
Resolution Note (6000.0.X):
Default references only works in EditMode, if they are used in PlayMode they will be null. But Default References have another behavior when in Editor-Only assemblies (ie. /Editor folder when not using Asmdef's, or Asmdefs only compatible with the Editor).