Search Issue Tracker
Won't Fix
Votes
6
Found in
2021.3.37f1
2022.3.30f1
6000.0.3f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
7000.0.0a1
Issue ID
UUM-72333
Regression
No
Prefab overrides don't recover missing managed references
Reproduction steps:
# Open the attached “Repro“ project
# Open the “Assets/SceneB.unity“ Scene
# Replace all “StringContainer“ occurrences with “Container“ in the “Assets/SRBugDemonstrator.cs“ Script
# Open the “Assets/SceneA.unity“ Scene
# Select the “SRPrefabInstance“ GameObject
# Observe the “Managed Reference 1” inside the Inspector (Debug mode enabled)
# Replace all “Container“ occurrences back with “StringContainer“ in the “Assets/SRBugDemonstrator.cs“ Script
# Observe the “Managed Reference 1” inside the Inspector (Debug mode enabled)
Expected result: The reference is not null and references the old StringContainer
Actual result: The reference is still null and is not able to resolve the old reference
Reproducible with: 2021.3.37f1, 2022.3.30f1, 6000.0.3f1
Reproducible on: M1 MacOS 14.4.1
Not reproducible on: No other environment tested
Note: Closing and reopening the “SceneA.unity” Scene fixes the issue
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
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.