Search Issue Tracker
Fixed
Fixed in 2020.3.X
Votes
0
Found in [Package]
2018.4
2019.4
2019.4.19f1
2020.3
2021.1
2021.2
Issue ID
1337143
Regression
No
[Perforce] Folder renaming with letter case changes are not properly detected
Reproduction steps:
1. Create a new Unity and connect it to a perforce server
2. Create a new folder inside the Assets folder of Unity project
3. Create or add any file inside the just created folder
4. Submit all changes to perforce
5. In Unity try to change the case of one of the letters of the folder you created (Example from 'Folder' to 'folder')
6. Click 'yes' on the prompt window (it will say that you are renaming a file that is under VC)
7. In P4V client hit refresh
Expected result: the files in the old folder should be recorded as move/delete, and files in the new folder should be move/add
Actual result: Unity does not record the deletion of the old folder or the creation of the new folder (the folder disappears from P4V entirely)
Reproducible with: 2018.4.35f1, 2019.4.26f1, 2020.3.8f1, 2021.1.7f1, 2021.2.0a17
Notes:
1. There are videos in edits
2. The issue does not occur when changing the name of the folder (just the case of the letter)
Comments (1)
-
unity_2C388DFAE4D7B17BA3CC
Nov 02, 2023 15:53
Did you just fix it in the two version above? Seems to still happen in 2021.3.28f1.
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
- Shader warnings are thrown when deleting blocks in the Ribbon VFX Graph
- Shadow casters are not rendered when deploying builds in specific Unity 6.0 versions
- Automatically unfocuses when focusing and DropdownField is open
- Debug Draw Mode stops rendering GameObjects when GPU Resident Drawer is enabled
- Only a single Selector is added to a Container when drag and dropping multiple of them on an Element in UI Builder
Resolution Note:
Folder case-renaming are now properly detected by Perforce on a case-sensitive server (Linux)
Fixed in: 2022.2.0a7
Resolution Note (fix version 2020.3):
Fixed in 2020.3.33f1