Search Issue Tracker
Fixed in 2018.4.3f1
Fixed in 2017.4, 2018.4, 2019.1, 2019.2
Votes
0
Found in
2018.3.0a1
2018.3.6f1
2019.1.0a1
2019.2.0a1
Issue ID
1131599
Regression
No
[Perforce] Reverting the ProjectVersion file marks it as Read-only preventing any further updates
How to reproduce:
1. Create a new project and set it up to use Perforce's version control (With an older version, for example, 2019.2.0a8)
2. Observe the "ProjectVersion.txt" file in the ProjectSettings directory (It is writable and shows the correct 2019.2.0a8 version)
3. Update the project to a newer version (2019.2.0a9) and observe the ProjectVersion.txt file again (It is still writable and shows the correct 2019.2.0a9 version)
4. In Perforce revert the "ProjectVersion.txt" file
Expected result: the file shows the 2019.2.0a9 version in its log and is writable
Actual result: the file is now marked as "read-only" and updating the project to 2019.2.0a10 will not correctly update the file
Reproduced in: 2019.2.0a10, 2019.1.0b10, 2018.3.12f1
Note: When reverting the log also incorrectly shows the last used version as 2019.2.0a10 even when it was never launched in one
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
- Investigate why .meta files are sometimes not parsed right
- Cursor is not locked to Game window when pressing Windows key then clicking the Taskbar and refocusing the Game
- EditorGUIUtility.ShowObjectPicker doesn't allow to pick assets from derived classes
- Disabling and enabling an AudioSource component controlled by a Timeline causes a pop and ignores the mixer settings
- Build Pipeline functions cause a re-execution of the last Async task when called in an Async function
Resolution Note (fix version 2018.4.3f1):
Fixed in: 2018.4.3f1, 2019.1.7f1, 2019.2.0b6, 2019.3.0a1