Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.27f1
2022.3.1f1
2023.1.0b20
2023.2.0a18
2023.3.0a3
6000.0.0b11
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
7000.0.0a1
Issue ID
UUM-17945
Regression
No
A new asset becomes untracked in Perforce when 'StartAssetEditing' and 'RemoveAndWrite' are called twice
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
This issue will be revisited in 6 months. We will take into account while we prepare to create a better P4 plugin.