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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0a14