"Cannot find Action Map 'Player' in actions '...inputactionasset'

I renamed the default player map from ‘Player’ to ‘Walking’ in my inputactionasset.
I double-checked that the PlayerInput instance knew the new name, and the Inspector showed it switched automatically to ‘Walking’.

I start Play, and the keyboard responds correctly but the mouse fails to have any effect, and the console shows:

Cannot find action map ‘Player’ in actions ‘GenericPlayerInputs (UnityEngine.InputSystem.InputActionAsset)’
UnityEngine.InputSystem.PlayerInput:OnEnable () (at Library/PackageCache/com.unity.inputsystem@1.4.4/InputSystem/Plugins/PlayerInput/PlayerInput.cs:1619)

The source code line in PlayerInput does not obviously have a reference to the old name ‘Player’.

            using (InputActionRebindingExtensions.DeferBindingResolution())
            {
                AssignPlayerIndex();
                InitializeActions();
                AssignUserAndDevices();
                ActivateInput();       << line 1619
            }

If I rename the action map back to ‘Player’ everything works again.

I have the same issue. Has anyone a solution.

Same problem, bumping

Same problem, bumping

If anyone still has this error, this fixed the problem for me:
https://stackoverflow.com/a/64674245

The solution is to go to the PlayerInput component, change the default map, save, change it back again. This refreshes the Editor internals.

jakesee Thank you for the solution!
Worked for me!

This problem appears as a result of renaming to Input Actions the Map Action. If the script has field type string with the name of the action map, then you will need to fix it.
Look for this method to identify the problem:

public void SwitchCurrentActionMap(string mapNameOrId)

Original text:
Данная проблема появляется в следствии переименования в Input Actions Map Action. Если в скрипте есть тип поля string с именем Action Map то надо будет исправить.

Still happening in Unity 6.000.48f1 in 2025. Very annoying. Thanks for the info on how to fix this. Has anyone reported this as a bug yet? Would be nice to know so we can vote on it.