Search Issue Tracker
Fixed
Fixed in 2021.3.25f1, 2022.2.16f1, 2023.1.0a21
Votes
0
Found in
2021.3.8f1
2022.2.0b6
2023.1.0a6
Issue ID
UUM-13245
Regression
Yes
SerializeReference instance added through PropertyModifications can cause non-deterministic builds
If you have PropertyModification coming from 2020 version and inserting a SerializeReference instance
- target: {fileID: 4710738598204243869, guid: 4b895725f74b74a8cba03723bdbd90ac,
type: 3}
propertyPath: _Foo.m_LocalVariables.Array.data[1].variable
value: Unity.Localization UnityEngine.Localization.SmartFormat.PersistentVariables.IntVariable
objectReference: {fileID: 0}
Then doing a Scene AssetBundle build or Player build containing a scene containing that PropertyModification it will generate new unique ids for those instances.
In 2021.2 and above the new format will be stable for inserting instances as it provides the ManagedReference id:
- target: {fileID: 52625195582723116, guid: d7f55dfe8d2b08a478db87d6a76d1bd0,
type: 3}
propertyPath: managedReferences[4254687138008530948]
value: Unity.Localization UnityEngine.Localization.SmartFormat.PersistentVariables.IntVariable
objectReference: {fileID: 0}
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
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Resolution Note (fix version 2023.1.0a21):
Serialization: PropertyModifications created prior to 2021.2 creating SerializeReference instances are now generating deterministic ids during builds.