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
- Camera.allCameras returns cameras from all loaded Scenes when using multi-Scene setup
- Camera.layerCullDistances has no effect when GPU Resident Drawer is enabled
- ARM64 and ARMv7 APKs return the same version code when "Split APKs by target architecture" is enabled
- Crash on ProfilerMutexLock when closing a project with specific Assets
- “Callback unregistration failed. Callback not registered.” is thrown when changing layouts with two "Font Asset Creator" windows docked
Add comment