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
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
- Highlighter.Highlight does not find elements in an array or list when the array or list is collapsed
- [URP][NRP] RenderPass, BeginSubPass, and EndRenderPass errors are thrown when Native RenderPass is enabled
- D3D11 swapchain error pop-up appears and the Editor shuts down when Generating Lighting with Probe Volumes present
CyanSlinky
Oct 25, 2018 21:01
This is still broken in 2018.2.6f1 and 2018.2.12f1 and i cant for the life of me fix it, it's really starting to annoy me.
zero3growlithe
Oct 16, 2018 17:17
If error can't be removed, at least give us the option to find the file causing this error...
kyrnen
Aug 06, 2018 19:28
This problem occurs for me when I try to update my project on Unity 2018.2.2f1 as well.
Error appears 4 times in the console stating:
Unable to parse file ProjectSettings/ProjectVersion.txt: [mapping values are not allowed in this context] at line 1
devis
Jul 13, 2018 09:42
Confirmed that nuking the ProjectVersion.txt from every project you got on your PC will fix this.
You do get one fancy error about "Project Version Number" but that disappears after you re-start Unity again.
Mr_Rhetorical
Jul 06, 2018 17:04
I'm using this on version 2018.1.6f1 and I was able to replicate the issue.
bolt2009
Jul 03, 2018 08:49
iMac, unity hub with 5.6 and 2018.1.0f2
Use sourceTree to merge from github, update my game in unity5.6 yesterday;
Today I buy a "2D Under Water Pack - Handcrafted Art" package and create a new project in unity 2018.1.0f2, open its demo scene ana click the play button and my mac system crashed auto reboost the system, and when I open this project I got this error.
Mark on June.3rd, 2018
fotalik
May 05, 2018 17:34
Unity Version: 2018.1.0f
Operation system: Window 10, verison - 1709
Hi, i also have this issue. I just updated my project to from Unity 2018.1.0b Unity 2018.2.0b and got a lot of errors. Then i tried to reinstall Unity to 2018.1.0f and when i create a new project i have this error:
Unable to parse file ProjectSettings/ProjectVersion.txt: [Control characters are not allowed] at line 0
File data:
m_EditorVersion: 2018.1.0f2