Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.36f1
2022.3.21f1
2023.2.13f1
2023.3.0b10
Issue ID
UUM-65675
Regression
No
UnityYAMLMerge fails to parse and shows a "did not find expected key" error
How to reproduce:
1. Download and extract the attached “yamlmerge-bug-repro.zip” file
2. Run “run_mergetool.bat” found in the extracted folder
Expected result: The parsing is successful and the tool merges the attached files
Actual result: An error message stating “Error parsing file ‘LocalizationSO.asset.BASE’: did not find expected key” is shown
Reproducible in: UnityYAMLMerge 1.0.1 (2021.3.36f1, 2022.3.21f1, 2023.2.13f1, 2023.3.0b10)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
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
- [Search] Query Builder - uneditable NaN in Transform vectors
- Transform.rotation property is as a Vector4 Quaternion instead of a Vector3 field when using InspectorElement.FillDefaultInspector
- [Search] Query Builder - "Input String was not in a correct format" error when changing query options
- MacOS Xcode project build fails when a package has PrivacyManifest
- [IL2CPP] Crash when closing the Player while an exception is thrown during exception handling
Resolution Note:
The issue was caused by a '#' symbol in the target file, making UnityYAMLMerge unable to parse it.