Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2021.3.30f1
2022.3.10f1
2023.1.14f1
2023.2.0b11
2023.3.0a6
Issue ID
UUM-49558
Regression
No
Mono Behavior of serializable reference type gets created when selecting a corresponding object in the Hierarchy window if it’s null and the Inspector window is set to Debug mode
How to reproduce:
1. Open the user’s attached “TestInsectorProject.zip” project
2. Open “SampleScene” Scene (Assets > Scenes)
3. Enter Play Mode
4. Change the Inspector’s mode to “Debug”
5. In the Hierarchy window, select “TestInsector” GameObject
6. Observe the Console window
Expected result: “Is null: True” is logged
Actual result: “Is null: False” is logged
Reproducible with: 2021.3.30f1, 2022.3.10f1, 2023.1.14f1, 2023.2.0b11, 2023.3.0a6
Reproduced on: macOS 13.5.2 (Intel)
Not reproducible on: No other environment tested
Note: not reproducible with “Normal” Inspector mode
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Resolution Note:
When we use [NonSerialized] attritube instead than [Serializable] attritube, we get the class object value as NULL in both debug and normal inspector modes.
Resolution Note (2023.3.X):
When we use [NonSerialized] attritube instead than [Serializable] attritube, we get the class object value as NULL in both debug and normal inspector modes.