Search Issue Tracker
In Progress
In Progress in 2021.3.X, 2022.2.X
Fixed in 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
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
Resolution Note (fix version 2023.1.0a21):
Serialization: PropertyModifications created prior to 2021.2 creating SerializeReference instances are now generating deterministic ids during builds.