Search Issue Tracker
Fixed
Fixed in 2023.1.19f1, 2023.2.1f1, 2023.3.0a15
Votes
0
Found in
2023.1.0b14
2023.2.0a12
2023.3.0a3
Issue ID
UUM-33981
Regression
Yes
Moving an Asset with same name as a Folder in the destination causes naming conflict
Steps to reproduce:
1. Open attached project "Bug.zip"
2. In Project window, open Assets/Scenes/SceneName folder
3. In Project window, drag the "ScenName.unity" scene asset into the previous folder in the Hierarchy - Assets/Scenes
4. In Dialog window, press "Ok"
Expected result: No Dialog window, Scene Asset is moved and not renamed
Actual result: Dialog window, Asset is not moved and renamed
Reproducible with: 2023.1.0a1, 2023.1.0b14, 2023.2.0a12
Not reproducible with: 2020.3.47f1, 2021.3.24f1, 2022.2.17f1
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
- “[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
Resolution Note (fix version 2023.2.1f1):
Fixed in 2023.2.1f1