Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.1.0f2
Issue ID
1158736
Regression
No
Perforce Integration re-adds deleted files
How to reproduce:
1. Create a new project and set it up to use Perforce version control
2. Submit the project
3. In the Packages folder create a new text file
4. Close Unity and in Perforce add the newly created text file
5. In the depot, delete the added text file
6. Sync to the previous revision, when the file was added
7. Open the Unity project again, go to Window -> Asset Management -> Version Control
8. Observe the outgoing list
Expected result: the newly added text file is not automatically re-added
Actual result: the text file is automatically marked for add even when the "Automatic add" option is unchecked
Reproduced in: 2019.3.0a5, 2019.2.0b5, 2019.1.5f1, 2018.4.f1
Couldn't test with: 2017.4.28f1 (No packages folder in this version, checked with "UnityPackageManager" but it was not reproducible with it)
Note: This only reproduces with files in the Packages folder
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
- “Label” name in Sprite Library Editor window lacks character limit causing long names go under the Object Field
- Triangle icon in Animation window’s Property button is barely visible in dark theme
- Preview image (screenshot) is not available after capturing snapshot in Memory Profiler
- Crash on UNITY_FT_Stream_ReadAt when changing TMPro properties after unloading an AssetBundle
- Particles spawn at the same position when using raw byte address buffer in VFX Graph
Resolution Note:
This is by design.
The file is marked for delete on the server, but the local user has not updated to the server status, thus it's shown as deleted on the incoming list.
It's marked for add locally, however, the user is out of sync with the server status.
I.e. The local user sees the head action as marked for delete, but the file is added in their local project.