Unity Issue Tracker - A new asset becomes untracked in Perforce when 'StartAssetEditing' and 'RemoveAndWrite' are called twice
Closed
UUM-17945
A new asset becomes untracked in Perforce when 'StartAssetEditing' and 'RemoveAndWrite' are called twice
Unity: Version Control
Won't Fix
6.5.X
6.4.X
6.3.X
6.2.X
6.1.X
6.0.X
2023.3.X
2023.2.X
2023.1.X
2022.3.X
2021.3.X
Cancelling: the 6000.1 version has reached its end of life. If you need additional fixes, please upgrade to a newer Unity version.
Cancelling this 2023.2 tech release issue since the support for this release has come to end of life. Cancelling this 2023.2 port case does not affect any LTS or Unity 6 Beta/Preview that remain open.
Reproduction steps:
1. Open the attached 'PerforceTestProject' project
2. Go to the 'Edit -> Project Settings'
3. In the Version Control section select Perforce as the Mode and enter credentials to connect to the Perforce
4. Go to the 'Assets -> P4RemoveAndWriteWithAssetEditing'
5. Note that the 'p4testWithAssetEditing.txt' file is created and 'Added Local'
6. Go to the 'Assets -> P4RemoveAndWriteWithAssetEditing'
Expected result: The 'p4testWithAssetEditing.txt' file is 'Added Local'
Actual result: The 'p4testWithAssetEditing.txt' file is untracked