Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.1.0b7
Issue ID
1002476
Regression
No
Saving upgraded project doesn't update the ProjectVersion.txt if no changes are made
How to reproduce:
1. Create a new project in any Unity version
2. Open the same project in new Unity version
3. File > Save Project
4. Exit Unity
5. Open the ProjectVersion.txt inside "ProjectSettings" folder
Actual result: Unity doesn't update the project's Editor version.
Expected result: Unity should update the project's Editor version after pressing Save Project.
Reproducible with: 2018.2.0a6, 2018.1.0b13, 2017.4.1f1, 2017.3.2f1, 2017.2.2p2, 2017.1.3p2.
Notes:
Editor version is updated if any changes are made inside the project.
-----------------------------------------------------
fixed in 2018.3.0a1
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- Package Manager Filters (Status) dropdown is different color than Packages, Sort or Add package dropdowns
andisopany
Jul 13, 2018 20:18
Just a warning to everyone that this may lead to a broken project.
In my case I upgraded to 2018.2 but didnt save anything, then by mistake opened with a previous version of unity. Many of my prefabs are now broken which is forcing me to revert about a weeks worth of work.
LW
Jun 12, 2018 13:31
This is still a bug and is not fixed.