Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
2019.3.0a12
Issue ID
1175295
Regression
No
[VCS] Files with a conflicted state do not update their status until the Editor is refocused
How to reproduce:
1. Create a new project in your preferred workspace and connect it to Perforce
2. Create a new empty script and submit the project (This will be User 1)
3. Open the same project with a different user in a different workspace as well (This will be User 2)
4. With the User 1 checkout the empty script and edit in a comment at any line
5. On the User 2's project checkout the same empty script and add a comment at a different line
6. Submit the User 2's version of the file to the depot
7. On the User 1 do "Get Latest" on the empty script
8. Observe its status (It should now have the conflicted state but instead says It's out of sync)
9. Unfocus the Editor and re-focus to it
10. Observe its status again
Expected result: the file's status is updated immediately after "Get Latest" is clicked
Actual result: the conflicted file's status isn't updated until the Editor is refocused
Reproduced in: 2019.3.0a12, 2019.2.1f1, 2019.1.14f1, 2018.4.6f1, 2017.4.31f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
Add comment