Search Issue Tracker
Won't Fix
Votes
4
Found in
2023.3.0a12
6000.0.0b11
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
7000.0.0a1
Issue ID
UUM-17930
Regression
No
[Perforce] File that is deleted at later revision is marked for add when the file is added back by syncing with older revision
How to reproduce:
1. Create a new Unity project
2. Set the Version Control Mode to Perforce
3. Connect to a working perforce server
4. Create a new script called Test.cs
5. Submit the added file (and its meta file) to the perforce server - call this changelist A
6. Delete Test.cs (and its meta file)
7. Submit the change to the perforce server - call this changelist B
8. Within P4V (perforce's standalone client), sync the local workspace to changelist A
9. Return to the Unity Editor
Expected result: Test.cs is not marked for add
Actual result: Test.cs is now marked for add
Reproducible with - 2018.4.35f1, 2019.4.27f1, 2020.3.11f1, 2021.1.9f1, 2021.2.0a18
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
We will evaluate this in the next 6 months as we plan to improve the P4 integration in the Editor.