Search Issue Tracker
Active
Votes
3
Found in
2018.4
2019.4
2020.2.1f1
2020.3
2021.1
2021.2
Issue ID
1326156
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
- ShaderUtil.GetShaderData(shader).SubshaderCount does not count unsupported subshader
- GameObject.GetComponents returns the wrong number of components
- GUI button looks different from Editor in a Build
- Live Profiler Timeline keeps losing frame data while scrolling inside Profiler window
- Input.mouseScrollDelta.y is not correctly mapped to mouse wheel when running an iOS app on Apple Silicon Mac
Add comment