Search Issue Tracker
Fixed
Fixed in 1.8.0
Votes
0
Found in [Package]
1.8.0-pre.2
Issue ID
ISXB-743
Regression
No
"Expected a visual element called 'control-schemes-toolbar-menu' of type 'UnityEditor.UIElements.ToolbarMenu' to exist but none was found." is thrown when opening the Input Settings after closing the Input Actions window
How to reproduce:
1. Open the attached project
2. Select "Player" in the Hierarchy window
3. Click "Open" under the "Player Input" Component in the Inspector window
4. Close the Project Settings window
5. Click "Open Input Settings" under the "Player Input" Component in the Inspector window
Expected results: No errors are thrown in the Console window
Actual results: "Expected a visual element called 'control-schemes-toolbar-menu' of type 'UnityEditor.UIElements.ToolbarMenu' to exist but none was found." is thrown
Reproducible with: 1.8.0-pre.1 (2021.3.35f1, 2022.3.19f1, 2023.2.8f1), 1.8.0-pre.2 (2021.3.35f1, 2022.3.19f1, 2023.2.8f1, 2023.3.0b6)
Could not test with: 1.7.0 (no Input Actions tab in the Project Settings)
Reproducible on: Windows 11 22H2
Not reproducible on: No other environment tested
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 1.8.0):
This issue was fixed internally with ISX-1721.