Search Issue Tracker
Fixed
Fixed in 3.2.0-pre.4
Votes
0
Found in [Package]
3.2.0-pre.3
4.0.0-pre.1
Issue ID
TMPB-83
Regression
Yes
[Oculus][TMP] ArgumentOutOfRangeException Selection is out of range for UnityEngine.TouchScreenKeyboard on Quest
Steps to reproduce:
1. Download the attached user's project "TMProInput2020.zip"
2. Make sure to target the Android platform
3. Make sure to follow the configuration shown in the attached "image.png" when it comes to the OVR Manager component
4. Build and deploy to the Oculus Quest 1/2
5. Perform a logcat to the Oculus Quest 2 device (I.e. adb logcat) and pipe it to an output file. (I.e. > output.txt)
6. Close the app and open up the output.txt to find the exception
Expected results: The exception for the touch screen keyboard should not appear as the touch screen keyboard is not even enabled
Actual results: The exception for the touch screen keyboard appears when the touch screen keyboard is not even enabled
Reproducible on: TMP 3.0.6, 4.0.0-pre.1 (2021.3.5f1, 2022.1.5f1, 2022.2.0a17)
Not reproducible on: TMP 2.1.6, 3.0.6 (2019.4.40f1, 2020.3.36f1)
Reproducible with these devices:
VLNQA00415 - Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, OS: 10
VLNQA00275 - Oculus Quest (Quest), CPU: Snapdragon 835 MSM8998, GPU: Adreno 540, OS: 10
Notes:
-The user is not using any virtual system keyboard on the Oculus. This is not happening on 2020.3.x but it is happening on 2021.2.x. The user has also managed to work around this by changing all the prefabs' TMP Input field's hide soft keyboard field to true
-Could not get the build to run on a non-VR android device due to it requiring OVR Manager component to be enabled
-Exception:
ArgumentOutOfRangeException Selection is out of range.
Parameter name: selection
UnityEngine.TouchScreenKeyboard.set_selection(UnityEngine.RangeInt value)
TMPro.TMP_InputField.ActivateInputFieldInternal()
TMPro.TMP_InputField.LateUpdate()
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note (fix version 3.2.0-pre.4):
Resolved exception thrown when focusing on the InputField when the OVR use internal keyboard is off. Followed the uGUI solution to address the same bug.