Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
4
Found in
2023.3.0a12
6000.0.0b11
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment