Search Issue Tracker
Active
Fixed in 6000.0.0b16
Under Consideration for 2022.3.X
Votes
5
Found in
2022.3.28f1
6000.0.0b12
Issue ID
UUM-67893
Regression
No
[Quest] Native virtual keyboard does not show input and does not close or pass values to the input field when built on Quest
Reproduction steps:
1. Open the attached project "ReproProj"
2. Build and Run on Quest the “Assets/Scenes/DemoScene.unity“ Scene
3. In Player, click on one of the input fields
4. Write any text
5. Close the keyboard by pressing the blue Button with a checkmark icon
Expected result: The keyboard shows text and can be closed with the text present in the input field
Actual result: The keyboard is not showing typed-in text and cannot be closed or typed-in text is present on the keyboard but does not enter into the input field
Reproducible with: UGUI 2.0.0 (6000.0.0b13)
Could not test with: UGUI 1.0.0 (2022.3.22), UGUI 3.0.0-exp.3 (2023.2.15f1, 6000.0.0b13) (Keyboard does not appear)
Reproducible on:
VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Note:
- Could not test with Windows Standalone Player or in Play Mode due to keyboard not appearing
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Add comment