Search Issue Tracker
Active
Planned for 3.2.X, 4.0.X
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()
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [2020.3] Play Mode has visual artifacts when Graphics API is set to DirectX12 with Dynamic Resolution enabled
- White texture appears when setting “RenderTextureFormat.Depth” to “RenderTexture” on the Camera
- Cursor is visible when using “Cursor.lockState = CursorLockMode.Locked” and “Cursor.visible = false”
- Material.SetOverrideTag setting LightMode tag has no effect
- Decal is not rendered when in Camera component Culling Mask dropdown field Default is unselected
Add comment