Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
2020.1.0a3
Issue ID
1181370
Regression
No
[VCS] Files in VCCache remain mapped to wrong name after renaming (move task)
How to reproduce:
1. Create a new project in your preferred workspace and open it
2. Connect it to Perforce and uncheck "Automatic Add" if It's checked
3. Create a new folder and observe its status (should have a red dot indicating that it's a local file)
4. Change its name
5. Observe its status again
Expected result: the renamed folder is still marked as "local"
Actual result: the renamed folder loses its status and no longer has any version control icons on it
Reproduced in: 2020.1.0a3, 2019.3.0b2, 2019.2.3f1, 2018.4.8f1, 2017.4.32f1
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0a14