Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2020.3.46f1
2021.3.20f1
2022.2.9f1
2023.1.0b7
2023.2.0a5
Issue ID
UUM-29303
Regression
No
A change in source control is not registered when the names of two assets are swapped
Reproduction steps:
1. Open the attached “unity-asset-rename-test_clean.zip” project
2. Open the Command Prompt in the project’s folder
3. Run “git reset --hard” and then “git status” in the Command Prompt
4. Observe that the git tree is clean and there’s nothing to commit
4. Open the “/Asset/NameTest” folder in the Project window
5. Rename the “A” Asset to “X”
6. Rename the “B” Asset to “A”
7. Rename the “X” Asset to “B”
8. Run the “git status” command in the Command Prompt
Expected result: Asset meta files are not ignored and both “A.asset”, “B.asset” and their meta files are recognized as modified
Actual result: Asset meta files are ignored and only “A.asset”, “B.asset” are recognized as modified
Reproducible with: 2020.3.46f1, 2021.3.20f1, 2022.2.9f1, 2023.1.0b7, 2023.2.0a5
Reproducible on: Windows 10 (21H2)
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
The user has been presented with a workaround for this behavior, and after discussions amongst the team, we have agreed to close this bug as won't fix.
Resolution Note (2023.2.X):
The user has been presented with a workaround for this behavior, and after discussions amongst the team, we have agreed to close this bug as won't fix.