Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X
Won't Fix in 2023.2.X
Votes
4
Found in
2023.3.0a12
6000.0.0b11
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (2023.2.X):
Closing as Won't fix due to 2023.2 reaching it's EOL.