Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
5.6.0p3
Issue ID
906061
Regression
No
Editor keeps spamming error "Unable to parse YAML file: [mapping values are not allowed in this context] at line 1
Steps to reproduce:
1. Open user attached project "Trunk.zip"
2. Observe the errors in console window: "Unable to parse YAML file"
Expected result: Error should not appear
Actual result: Error appears after opening the project
Reproducible in: 2017.1.0b3, 5.6.0p4, 5.5.3p2, 5.4.5p1
Comments (2)
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
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
- Audio Mixer “+” buttons overlap with UI when the Audio Mixer window layout is set to Horizontal
- "Clear" button in the "Set project display name" closes all the pop-up instead of clearing just a name from the field
- Video Player renders no video on specific devices when using Vulkan
- The Editor slows itself down by showing tons of warnings when the majority of TransformAccessArrays content are NullRefs
hippogames
Feb 01, 2018 15:11
Deleting Unity registry folder has helped for me: HKEY_CURRENT_USER\Software\Unity\
ThatManOverThere
Sep 12, 2017 21:43
this is late but i had a similar problem with yaml file. any new project would have it as well but old scenes before the problem emerged wouldnt have it unless i saved the scene
this was just before i did some general clean up getting rid of stuff that i dont use. i like to keep about 95% of the hd open . so i got rid of steam since i dont ever use it any more and the last 3 things i bought i hated.
the yaml bug went away. cant explain it since the 2 shouldnt ever be talking to one another but i might have got a virus who was hanging out in a folder in steam and when i cast that stuff into the abyss it broke the connection