Type of instance in array does not match expected type

I just upgraded my project from 2021.3.7f1 to 2021.3.8f1. Now I keep getting this error message when running my game.


It doesn't seem to cause any problems in my game but it's annoying and makes it harder to read the console. I can't find any posts online for how to fix it so I'm asking here.

Edit:
Reverting the editor back to 2021.3.7f1 and the InputSystem back to 1.3 is the only solution I could find so far.

 

I'm facing the same problem in 2021.3.8f1 after upgrading. I need to switch between different input systems in the app, and this error is thrown when disabling a GameObject with PlayerInput attached.

The error comes from PackageCache\com.unity.inputsystem@1.4.1\InputSystem\Actions\InputBindingResolver.cs line 638: Debug.Assert(type.IsInstanceOfType(array[count]), "Type of instance in array does not match expected type");

A workaround is to use direct reference to the PlayerInput class instance and use enable/disable.

var playerInputs = GetComponent<PlayerInputs>();

playerInputs.enabled = false;

 

+1 can confirm this is on the latest version of Unity. It doesn't seem to be any configuration of my scripts or the input manager. I can't debug because its in the package manager.

 

Same error, is there any fix so far? If I disable Player Input it throws the error again...

 

This error is really annoying. It's still showing up in Input System 1.4.2
Had to revert to 1.3.0.

 

This seems to be an issue with template for editor version 2021.3.8f1. The one included with editor version 2021.3.5f1 it does not happen.

 

The workaround by @jmastorm didn't work for me. I wrote a similar one. Just put this script above the PlayerInput component causing the issue:

Code (CSharp):

1. using UnityEngine;
2. using UnityEngine.InputSystem;
3.  
4. public class PlayerInputErrorWorkaround : MonoBehaviour
5. {
6.     private PlayerInput Input;
7.    
8.     private void Start()
9.     {
10.         Input = GetComponent<PlayerInput>();
11.     }
12.  
13.     private void OnDisable()
14.     {
15.         Input.actions = null;
16.     }
17. }
18.  

 

Thanks, @erikDo. This worked perfectly for me.

 

Wait, so reordering components also affects their execution order? Had never realized this before

Anyway this worked for me, thanks

 

Just upgraded to 1.4.2 and getting this error. What exactly is causing this error? The workaround above is not working for me.

 

Found this. Appears to be "in progress", but they also comment that it doesnt appear to break anything, which means I dont know how much they will care to fix it quickly.

https://issuetracker.unity3d.com/is...type-error-appears-when-exiting-the-play-mode

 

Using the 3d tutorial and adding an empty script and nothing else was enough for me to get 7 messages relating to PlayerInput.cs

Unfortunately for me, this is happening all over the place for me, using 2d or 3d tutorials with a lot of pre-packaged code, works fine. Make a little bit of code in a new script and boom the whole house of cards comes down, though, somewhere else. It also appears to be totally unrelated and it's always the pre-packaged code that bombs.

 

Downgrading to Input System 1.3.0 did the trick for us.

 

Same with unity 2021.3.9f1 and latest Unity Input System 1.4.2. Will downgrade

 

It's been indicated that they won't fix this in 1.4.x (https://issuetracker.unity3d.com/issues/upgrading-to-1-dot-4-1-throws-errors-for-keyboard-use)
I suggest voting the bug up the priority list as there are knock-on effects from being forced to update the editor to use a beta 1.5.x version

 

I've added // in front of the line that sends the error message - the script is InputBindingResolver.cs in Library\PackageCache\com.unity.inputsystem@1.4.1\InputSystem\Actions
It might prevent the script from throwing real errors but... fixed this issue for now.

 

...and that didn't help

 

Whenever I edit a packages source, I get the message: "The package cache was invalidated and rebuilt because the following immutable asset(s) were unexpectedly altered" and it gets reset. I guess I need to edit not only the package in the editor, but also the one in the download cache.

 

FYI: for anyone getting this error, try this:

Inside Project Settings > InputSystem: I found this huge button labeled Create Settings Asset.
Did not receive an error after generating the script.

 

I already use the auto generated asset. I wonder if your post indicates that it needs to be deleted to force a full re-generation? Will try later today.

 

Thanks ! That also works perfectly for me !

 

Hi all,

InputSystem 1.4.1 and 1.4.2 are indeed both bonkers. There are the issues mentioned here and also I think some strange missed input issues as well. I didn't test for long because I noticed multiple issues and simply have no idea where to begin with things.

If anyone forgot how to revert packages,

1. Open the Package Manager
2. click on the + icon
3. Add package from GIT url...
4. com.unity.inputsystem@1.3.0

This did not work for me.

 

This worked for me also. Thank you!

 

They should care as it results in many developers wasting hours (which equates to money) tracking down whether this is a real issue or not. If I see errors, I first assume I didn't implement something correctly.

 

Thanks! This did the trick for me

 

Had a similar problem with the OnDisable errors popping up. Additionally one of the actions stopped firing events (Composite Action of WASD) after disabling and re-enabling its associated Action Map - unsure whether these errors are related, but both started occuring at the same time

Was all resolved by reverting to 1.3.0.

Thanks @Catsploration for the suggestion!

 

There is an issue with composite actions after upgrading to 1.4.x. We noticed that the same composites in different action maps are conflict to each other. Let's say you have an UI action map with WASD composite to navigate UI elements and a gameplay action map with WASD composite to move a character. In this case UI handles all input but gameplay receives nothing. We can't disable UI action map because we have intractable UI overlay which is active during gameplay. I'm not sure if this issue is related to the errors on exit play mode but these two issues came together.

 

I have the same problem by reloading the Scene (
SceneManager.LoadScene(SceneManager.GetActiveScene().name, LoadSceneMode.Single) )
, I tried all the suggested solutions, Lucky I'm just started with the new Input system so my solution is getting back to the classic Unity Input.

 

This is fixed in 1.4.4, so upgrading the InputSystem package resolves the issue
https://issuetracker.unity3d.com/is...type-error-appears-when-exiting-the-play-mode

 

What version of unity do you have?

 

I tried, but it didn't help