Search Issue Tracker

Active

Votes

0

Found in [Package]

2019.4

2020.3

2020.3.25f1

2021.2

2022.1

2022.2

Issue ID

1419112

Regression

No

A new asset becomes untracked in Perforce when 'StartAssetEditing' and 'RemoveAndWrite' are called twice

Package: Version Control

-

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

Reproducible with: 2.0.0-preview.22 (2019.4.36f1), 1.15.17 (2020.3.33f1, 2021.3.0f1, 2022.0b16, 2022.2.0a10)

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.