Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0a11
2020.1.0a1
2020.1.0a7
Issue ID
1188186
Regression
Yes
[VCS] VCS Context menu fails to show up and throws an error after upgrading project from 2019.3.0a11 and older versions
How to reproduce:
1. Create a new project with the 2019.3.0a11 or older version in your preferred workspace
2. Open it and connect it to Perforce
3. Close the project and open it with a 2019.3.0a12 or newer version
4. Try to rightclick assets in the VCS Window and observe the console
Expected result: the VCS Context menu shows up and no errors are thrown
Actual result: the VCS Context menu fails to show up and throws an "Menu CONTEXT/Change couldn't be found" error.
Reproduced in: 2020.1.0a7, 2019.3.0b5, 2019.3.0a11
Not reproducible in: 2019.3.0a10, 2019.3.0a1, 2019.2.7f2, 2018.4.10f1, 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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0a12