Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 2023.2.X, 2023.3.X
Votes
0
Found in
2021.3.27f1
2022.3.1f1
2023.1.0b20
2023.2.0a18
2023.3.0a3
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)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment