Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.34f1
Issue ID
UUM-18989
Regression
Yes
[Quest 2] Bluetooth keyboard cannot enter text into Unity UI input fields on Quest on Unity 2020.3.34f1 and later
Steps to reproduce:
1. Open the attached user's project "ReproOculusBrokenTyping.zip"
2. Open the sample scene "SampleScene.unity"
3. Build for Quest 2
4. Connect a BT keyboard and enter text into the Input Field
Reproducible on: 2020.3.34f1, 2020.3.41f1
Not reproducible on: 2020.3.33f1
Reproducible on these devices:
Quest 2
Notes:
-A Bluetooth keyboard is required to reproduce the issue
-Works fine on 2020.3.34f1 in PC VR (Link) when using a regular USB keyboard
-Test project was created from scratch in 2020.3.36f1, there are no C# scripts in the app and all properties are set to default. The EventSystem is set to give initial focus to the input field
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
There are no fixes planned for this Bug