Search Issue Tracker
Fixed
Fixed in 1.11.2, 7000.0.0
Votes
3
Found in [Package]
1.7.0
1.8.0-pre.1
1.8.0-pre.2
Issue ID
ISXB-687
Regression
No
ArgumentOutOfRangeException is thrown when the Input System UI Input Module Component is disabled from the Simulator using UI Button through
How to reproduce:
1. Open the “IN-60236_repro“ project
2. Open the “StartUp“ scene
3. Open the Simulator tab (Window → General → Device Simulator)
4. Enter Play Mode
5. In the Simulator tab press the “Button“ GameObject
6. Observe the Console
Expected result: No exceptions are thrown
Actual result: ArgumentOutOfRangeException is thrown
Reproducible with: 1.6.3 (2021.3.29f1), 1.7.0 ( 2021.3.32f1, 2022.3.13f1, 2023.1.20f1), 1.8.0-pre.1 (2023.2.0f1), 1.8.0-pre.2 (2023.3.0a14)
Reproducible on: Windows 10
Not reproducible on: No other environment tested
Notes:
* Not reproducible in Player
* Error: ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: index
UnityEngine.InputSystem.Utilities.InlinedArray`1[TValue].get_Item (System.Int32 index) (at ./Library/PackageCache/com.unity.inputsystem@1.7.0/InputSystem/Utilities/InlinedArray.cs:73)
UnityEngine.InputSystem.UI.InputSystemUIInputModule.RemovePointerAtIndex (System.Int32 index) (at ./Library/PackageCache/com.unity.inputsystem@1.7.0/InputSystem/Plugins/UI/InputSystemUIInputModule.cs:1861)
UnityEngine.InputSystem.UI.InputSystemUIInputModule.Process () (at ./Library/PackageCache/com.unity.inputsystem@1.7.0/InputSystem/Plugins/UI/InputSystemUIInputModule.cs:2177)
UnityEngine.EventSystems.EventSystem.Update () (at ./Library/PackageCache/com.unity.ugui@1.0.0/Runtime/EventSystem/EventSystem.cs:530)
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
Resolution Note (fix version 7000.0.0):
Merged into neutron. Fix did not differ from other ports