Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.21f1
2022.2.11f1
2023.1.0b8
2023.2.0a6
Issue ID
UUM-30453
Regression
Yes
Rid values are changing when trying to override a serialized managed reference value
Reproduction steps:
1. Open the attached project “SerializedRefsTest”
2. Open the “Assets/Scenes/SampleScene” scene
3. In the Hierarchy window select “TestPrefab” Game Object
4. In the Inspector window in script “Test” under the “Child” dropdown change the value of the “Dummy Value” field
5. Click on the Overrides and Apply all.
Expected result: The values of prefab are overridden
Actual result: The Console throws an error “Trying to update the managed reference registry with invalid propertyPath”
Reproducible with: 2021.3.21f1, 2022.2.0a11, 2022.2.11f1, 2023.1.0b8, 2023.2.0a6
Not reproducible with: 2020.3.46f1, 2022.2.0a10
Reproducible on: macOS 13.1 (Intel), 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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
In the case of this example a SerializeReference instance is replacing an existing instance, which implies the existing instance is no longer there. Old PropertyModifications targetting that previous instance will no longer apply.
However if you only had a PropertyModification changing the value of the field and applying this down it would work as the user expects in the context of this bug description.
Resolution Note (2023.2.X):
In the case of this example a SerializeReference instance is replacing an existing instance, which implies the existing instance is no longer there. Old PropertyModifications targetting that previous instance will no longer apply.
However if you only had a PropertyModification changing the value of the field and applying this down it would work as the user expects in the context of this bug description.