Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
1.4.2
Issue ID
ISXB-280
Regression
Yes
Multiple errors are thrown in the Console window upon exiting the Play mode when the Input System package is installed
How to reproduce:
1. Open the attached project “IN-14456.zip“
2. Open the “SampleScene” Scene
3. Enter the Play mode
4. Exit the Play mode
Expected result: No errors are thrown in the Console window
Actual result: “Type of instance in array does not match expected type” and “ArgumentNullException: Value cannot be null” errors are thrown in the Console window
Reproducible with: 1.4.1, 1.4.2 (2020.3.39f1, 2021.3.8f1, 2022.1.14f1, 2022.2.0b6, 2023.1.0a8)
Not reproducible with: 1.3.0 (2020.3.39f1, 2021.3.7f1, 2022.1.11f1, 2022.2.0b3, 2023.1.0a3)
Couldn’t test with: 1.3.0 (2021.3.8f1, 2022.1.12f1, 2022.1.14f1, 2022.2.0b4, 2022.2.0b6, 2023.1.0a4, 2023.1.0a8) - package version is not supported
Reproduced on: Windows 10 Enterprise
Note: Disabling and Enabling a GameObject that has a Player Input component while in the Play mode will result in the same errors
-
Resolution Note:
Closing this as duplicate in favor of https://jira.unity3d.com/browse/ISXB-282 which has more detailed information and reproduction steps.
Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/ISXB-282
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
This is a duplicate of issue #ISXB-244