Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.4.X
Votes
40
Found in
2018.1.0b7
Issue ID
1002683
Regression
No
Merge conflict in ProjectVersion.txt causes 'Unable to parse file' error on any project opened
Steps to reproduce:
1. Start a new project
2. Open ProjectSettings/ProjectVersion.txt file of your newly created project
3. Write anything in ProjectVersion.txt file or cause a merge conflict to break it
4. Start another new project
5. Notice that the error is still present
Expected result: "Unable to parse file ProjectSettings/ProjectVersion.txt: [mapping values are not allowed in this context] at line 1" error is unclear and should not stay present with any project opened
Reproduced in: 2018.2.0a8, 2018.1.0f, 2017.4.1f1, 2017.3.2f1, 2017.2.2p1, 2017.1.3p2
Fixed in: 2019.1.0a6
Workaround: This issue is likely a merge conflict in one of the ProjectVersion.txt files. The error is still present on any new project opened, so for now, it is suggested going through the projects and finding the one ProjectVersion.txt file causing this and deleting it.
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
- Inspector's custom tooltip is displayed incorrectly when the name is truncated in UI toolkit
- Crash on ScriptableRenderLoopDraw when rendering a specific VFX in Play Mode
- The script is not renamed in the Project window when renaming and a compilation Error is present
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
Big_Lebovsky
Nov 04, 2024 07:54
Got this on Unity 6 version. 6000.0.25f1.
Unable to parse file Assets/_JAM/Settings/UniversalRenderPipelineGlobalSettings.asset: [Parser Failure at line 104: Expected closing '}']
And a bunch more lines from the same asset
Rikvee
Jun 02, 2023 21:03
Still getting this issue in 2021.3.2f1
Unable to parse file ProjectSettings/ProjectVersion.txt: [Parser Failure at line 1: Expected non empty YAML buffer]
Doesn't seem to break the game, but it is annoying.
cozyurt_unity
Jul 13, 2020 17:24
kedi ve köpek mamaları kedi kumu çeşitleri www.patilimama.com
enhawk
Jun 19, 2020 10:32
this is not fixed
Scandalon_NoReallyItsMe
Apr 03, 2020 01:20
I just encountered this error, 2018.4.19f1
New empty 3D project, reproduced it twice. Compared file to existing project, identical. Deleting it solved the issue.
fr123234ee
Dec 29, 2019 02:36
have this problem in unity 2018.4.6
karimkos
Oct 17, 2019 21:29
Still, I have this problem in Unity version 2019.2.7f2.
Unable to parse file ProjectSettings/ProjectVersion.txt: [mapping values are not allowed in this context] at line 1
limonad76
Aug 06, 2019 17:41
Still have this error message in 2019.2.0f1 immediately after creating new 3D project.
Unable to parse file ProjectSettings/ProjectVersion.txt: [mapping values are not allowed in this context] at line 1
Fengkaihao
Jul 23, 2019 13:38
Still having the issue in 2019.1.10f1.
I don't know if the issue is of the same cause, but here is mine:
"Unable to parse file ProjectSettings/ProjectVersion.txt: [mapping values are not allowed in this context] at line 2"
TomZet
Jul 04, 2019 13:42
I´m using Unity 2019.1.8f and it´s still there.
I got plenty of projects on my system so any hint on how to discover the one ProjectVersion.txt causing this problem would be cool. How does this one differ from correct ones?