Search Issue Tracker
Active
Votes
0
Found in [Package]
2019.3.0a1
2019.3.7f1
2020.1
2020.2
Issue ID
1253568
Regression
Yes
AssetDatabase RenameAsset does not throw "Destination path name does already exist" when called with asset pipeline version 2
How to reproduce:
1. Setup a perforce server and connect with the Editor
2. Checkout the files
3. In Project window, select Assets/Duplicate/AssetRenamer
4. In Inspector window, hit the button 'Rename Asset'
5. Observe Console window
Expected result: "Problem : [error] Can not move asset from ... to ... . Destination path name does already exist" is thrown
Actual result: "rename correctly" is pinrted
Reproducible with: 2019.3.0a1, 2019.4.1f1, 2020.1.0b13, 2020.2.0a15 (asset pipline mode Version 2)
Not reproducible with: 2018.4.24f1, 2019.3.16f1 (asset pipline mode Version 1)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment