Search Issue Tracker

By Design

Votes

1

Found in

2017.1.1f1

Issue ID

950980

Regression

Yes

ProjectVersion.txt doesn't get updated by 2017.1.1

Themes

-

Steps to reproduce:
1 create a new empty project
2 close the editor
3 change the content of ProjectSettings/ProjectVersion.txt to version 2017.1.0f3
4 open the editor (version 2017.1.1.f1) and observe the version of the project in the list of recent projects (2017.1.0)
5 open the project and accept project upgrade
6 close the editor
7 open the editor (version 2017.1.1.f1) and observe the version of the project in the list of recent projects (2017.1.0)

extra step: open ProjectSettings/ProjectVersion.txt and observe that it's not updated (2017.1.0f3)

Expected result:
project version upgraded in the list of recent projects after the upgrade
ProjectVersion.txt file updated with the version of the editor upgrading the project

Actual Result:
same project version in the list of recent projects
ProjectVersion.txt not updated with the correct editor version

It's not reproducible in version 5.4.6f1 and 2017.2.0b11
Reproduced in 5.6.2p4 and 2017.1.1f1

Workaround: set version manually in ProjectSettings/ProjectVersion.txt to the correct version to avoid project upgrade each opening

Comments (4)

  1. LW

    Jun 12, 2018 13:30

    This is a bug and is still not fixed.

  2. petrucio

    Apr 18, 2018 20:13

    By design?
    BY DESIGN!?
    B.Y. D.E.S.I.G.N !?!?!?
    Seriously?!?!?!?!

  3. Snorkel

    Oct 31, 2017 14:24

    Happens when upgrading from 5.6.1 to 5.6.2 or 5.6.2p4.
    How is this 'By design' ?

  4. pistha

    Sep 28, 2017 09:15

    I'm having the same problem with my project.

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.