Search Issue Tracker

Fixed in 2019.1

Planned for 2018.4

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

Themes

-

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.

Comments (11)

  1. 68c7dc7d14a334bb7860a7f339231371?d=mm

    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

  2. Eb6fcf70a1a2b1dd143d64795425fbd3?d=mm

    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"

  3. E644edde11dc2e768e44f48430a1cc2a?d=mm

    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?

  4. 361b5e7981634e9523a839fb90bd60ca?d=mm

    mailitos

    Nov 29, 2018 12:55

    Unity 2018.2.17f1 and the problem continues

  5. 7aa0991def8464ce83aa42d9c6db783f?d=mm

    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.

  6. Dc7e5d79777ee80af498e62ca1888aaa?d=mm

    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...

  7. 364fbf7a88408636ca2fa91ab0cfa646?d=mm

    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

  8. B10d60137013153df73a950a886a8910?d=mm

    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.

  9. 7980142674eab8f1ece48e93585d2ad2?d=mm

    Mr_Rhetorical

    Jul 06, 2018 17:04

    I'm using this on version 2018.1.6f1 and I was able to replicate the issue.

  10. 9eaa843e45343b7086dae22a12a843cb?d=mm

    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

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.