Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
2020.1.0a3
Issue ID
1181651
Regression
No
[VCS] Provider.ChangeSetMove and Provider.DeleteChangeSet don't refresh the VCS Window
How to reproduce:
1. Add the attached project ("ChangeSet issues.zip") to your preferred workspace and open it
2. Connect it to Perforce and submit the "add" material
3. Create a new empty Changeset
4. Replace the "enteridhere" parts in the NewBehaviourScript's lines 19 and 28 with the newly created Changeset's ID (The number that is shown next to the changeset in the VCS Window)
5. Check out the "add" material and go to "Simple Window" -> "ChangeSetMove"
6. Observe that the "add" material did not get moved right away (You have to refresh the VCS Window for changes to be seen)
7. Submit or Revert the "add" material to get it out of the way
8. Go to "Simple Window" -> "DeleteChangeSets" to try to delete the leftover empty changeset
9. Observe that it's still there (A refresh is needed)
Expected result: the changes made are immediately visible
Actual result: the changes made do not show up until the VCS Window is refreshed
Reproduced in: 2020.1.0a3, 2019.3.0b2, 2019.2.3f1, 2018.4.8f1, 2017.4.32f1
Note: Also, it would be nice if DeleteChangeSet could also take ChangeSet as an argument not just ChangeSets
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
- “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
Resolution Note (fix version 2020.1):
The Provider API will be reworked in the future. We've decided to update the documentation to better reflect the method's peculiarities instead:
Provider operations just execute the VCS commands, and do not automatically refresh the Version Control window. To update this window, use Task.SetCompletionAction