Search Issue Tracker
Active
Under Consideration for 1.16.X
Votes
1
Found in [Package]
1.16.0
Issue ID
OXRB-724
Regression
No
The Enter key is not displayed on TouchScreenKeyboard to allow new lines for TMP_InputField
How to reproduce:
1. Open the attached project "IN-125384"
2. Open scene “SampleScene“
3. Switch to Android platform
4. Build to Oculus Quest device
5. Use the Quest controller and point at the text input field in the scene
6. Press the Enter key
7. Observe to TouchScreenKeyboard
Expected result: The Enter key introduces new lines for a multi-line input field
Actual result: The Enter key registers the text within the input field and closes the keyboard
Reproducible with: 1.10.0 (6000.0.2f1), 1.16.0 (6000.0.63f1, 6000.2.14f1, 6000.3.0f1, 6000.4.0a5, 6000.5.0a2)
Reproducible on: Windows 11 Enterprise
Not reproducible on: No other environments tested
Reproducible on devices:
Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650
Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno (TM) 740 (reporter)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
Add comment