Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.40f1
2022.3.38f1
6000.0.11f1
6000.1.0a3
6000.2.0a1
6000.3.0a1
Issue ID
UUM-75832
Regression
No
A variable holding a GameObject reference becomes null when a variable of a SerializeReference object is applied to a Prefab
Reproduction steps:
1. Open the attached “ReproProj” project
2. Open the “Assets/SampleScene” scene
3. In the Hierarchy window, select the “GameObject” GameObject
4. In the “Test Script” Component, modify the “X” field value
5. Click the three dots menu for the Component and select “Modified Component” -> “Apply to Prefab ‘GameObject’”
6. Observe the “Go” field of the Component
Alternative reproduction steps:
1. Open the attached “ReproProj” project
2. Open the “Assets/SampleScene” scene
3. In the Hierarchy window, select the “GameObject” GameObject
4. In the “Test Script” Component, modify the “X” field value
5. Click on the “Overrides” button, select the “Test Script” and then hit the “Apply” button
6. Observe the “Go” field of the Component
Expected Result: The “Go” field does not lose its GameObject
Actual Result: The “Go” field loses its GameObject
Reproducible with: 2021.3.40f1, 2022.3.38f1, 6000.0.11f1
Reproducible on: Windows 11 Pro
Not reproducible on: No other environments tested
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
- Console shows Exception: {"error":"not found","detail":["not found"]} after opening Build History window
- [HDRP] Volumetric cloud shadows disappear when there is no directional light shadows
- “Selector” column names in the Search window are lowercase when added
- Install List Project Counter Panel can be right clicked through and Install Context Menu can be opened disabling Project Counter Panel's buttons
- [MacOS] Scene is marked/flickering as dirty (with asterisk) when dragging a Material on a GameObject in Scene view
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.