Search Issue Tracker
Fixed
Fixed in 6000.0.55f1, 6000.1.14f1, 6000.2.0b11, 6000.3.0a3
Votes
0
Found in
6000.0.47f1
Issue ID
UUM-107408
Regression
No
m_Modifications block serializes incorrectly when replacing source prefabs
The “m_Modifications” block in the “PrefabInstance” section changes serialization order constantly, as explained in this post: https://discussions.unity.com/t/we-keep-getting-annoying-redundant-change-to-the-order-of-prefabinstance-m_modifications/943063. The reason could be outdated overrides after replacing source prefabs. Reproduction is not necessary for this issue.
Note: Not reproduced by CQA
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
- [Android][iOS][UnityPlayerActivity] Legacy InputField.onEndEdit is not called when ending text edit
- Transform corruption and/or crash on PhysX::CreateCharacterController when spawning physics objects into Prefab stages
- UNITY_EDITOR data is Serialized into AssetBundle when building on the active Build Target
- "TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations..." error when changing the Packages "Cache Location" folder
- CompilationPipeline.assemblyCompilationFinished() hangs unity when reloading domain
Resolution Note (fix version 6000.3.0a3):
Fixed issue where m_Modifications block serializes incorrectly when replacing source prefabs.
Resolution Note (fix version 6000.2.0b11):
Fixed issue where m_Modifications block serializes incorrectly when replacing source prefabs.
Resolution Note (fix version 6000.1.14f1):
Fixed issue where m_Modifications block serializes incorrectly when replacing source prefabs.
Resolution Note (fix version 6000.0.55f1):
Fixed issue where m_Modifications block serializes incorrectly when replacing source prefabs.