Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.5.0
Issue ID
ISXB-418
Regression
No
Player Input Component doesn't update Default Map if the currently selected Action Map is deleted and the component's object is not Inspected
How to reproduce:
1. Open the attached user project “TestNewInputSystem.zip“
2. Open Scene “TestScene“ (Assets/Scenes)
3. Select the “MyInputActions“ asset in Assets and press “Edit asset“ in the Inspector
4. In the MyInputActions window, right click on the “ActionMap“ Action Map and press “Duplicate“
5. Delete the old “ActionMap“ Action Map
6. Enter Play Mode
Expected result: No errors in the Console
Actual result: “Cannot find action map 'ActionMap' in actions 'MyInputActions (UnityEngine.InputSystem.InputActionAsset)'“ error in the Console
Reproducible with: 1.4.4(2020.3.45f1, 2021.3.18f1, 2022.2.5f1, 2023.1.0b2), 1.5.0 (2020.3.45f1, 2021.3.20f1, 2022.2.9f1, 2023.1.0b5, 2023.2.0a4)
Reproduced on: macOS 13.0.1 (Intel)
Notes:
- Selecting the “Capsule” GameObject in the Hierarchy and selecting Default Map to “<None>“ in the “Player Input“ Component gets rid of the error
- Also talked about in Unity Discussions: https://discussions.unity.com/t/cannot-find-action-map-player-in-actions-inputactionasset/901010
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
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.