Search Issue Tracker
Not Reproducible
Votes
0
Found in
Not Applicable
Issue ID
UUM-131530
Regression
No
Prefabs are corrupted due to inline-styled YAML when UnityYAMLMerge is used to merge prefabs
How to reproduce:
- Locate the UnityYAMLMerge tool in “<Unity Editor version Path>\Editor\Data\Tools“ directory
- Copy the path to the UnityYAMLMerge tool
- Extract and open the “UnityYAMLMerge_BugReport.7z“ directory
- Edit the “reproduce_merge.sh“ in Notepad
- Change the value for “UNITY_YAML_MERGE“ with the path to the UnityYAMLMerge tool
- Save the changes and run the script
- Edit the “test_output/merged_output.prefab“ in Notepad
- Observe the lines 41103 - 41114 in the Notepad
Actual results: The array is listed in this format: [ {}, {}, {} ]
Expected results: The array is listed in this format:
- {}
- {}
- {}
Reproducible in: 2023.1.0a1, 6000.0.65f1, 6000.3.3f1, 6000.4.0b3, 6000.5.0a4
Reproduced on: Windows 11 Pro (25H2), macOS 15.7.2 (reported against)
Not reproduced on: No other environment tested
Note: Both array interpretations are correct YAML-wise, however, Unity accepts only the expected (block/list) type array
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment