Search Issue Tracker
Fixed
Fixed in 6000.0.0b16
Votes
5
Found in
2022.3.28f1
6000.0.0b12
6000.1.0a7
7000.0.0a1
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment