Search Issue Tracker
Fixed
Fixed in 1.10.0
Votes
0
Found in [Package]
1.8.1
1.9.0
1.10.0
Issue ID
ISXB-851
Regression
Yes
Error due to naming conflict is thrown when InputSystem Action Map is named "Debug"
Reproduction steps:
1. Open the attached “My project (133).zip” Project
2. Observe the Console
Expected result: No errors are thrown
Actual result: Error is being thrown due to the naming conflict
Reproducible with: 1.8.0-pre.2 (2021.3.37f1, 2022.3.22f1, 2023.2.17f1, 6000.0.0b13), 1.8.1 (2021.3.37f1, 2022.3.22f1, 2023.2.17f1, 6000.0.0b13)
Not reproducible with: 1.8.0-pre.1 (2021.3.37f1, 2022.3.22f1, 2023.2.17f1, 6000.0.0b13)
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Notes:
- Full error: “Assets\InputSystem.cs(65,15): error CS1061: 'InputSystem.DebugActions' does not contain a definition for 'Assert' and no accessible extension method 'Assert' accepting a first argument of type 'InputSystem.DebugActions' could be found (are you missing a using directive or an assembly reference?)”
- The Action Map menu is opened when double-clicking the “InputSystem.inputactions” from the Assets folder
- A reimport is needed after changing versions for the error to appear
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Graphics State Collection warm-up does not work when using with Addressables Shaders
- "Baked Shadow Radius" field is visible but inactive when when the Shadow Type is set to "Hard Shadows" under the Light Component
- Crash on OnDemandScheduler::HandleImportWorkerLogs when performing various Unity operations
- Caret is incorrectly offset when naming a file with a lot of characters in the Project window
- Point Cache window displays incorrect title “pCache” instead of full “Point Cache”
Add comment