Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.2.X
Votes
0
Found in
2020.3
2020.3.17f1
2021.1
2021.2
2022.1
Issue ID
1361663
Regression
No
[XR][Oculus] TouchScreenKeyboard reports state "Visible" even if the <uses-feature> is not defined in the AndroidManifest
Reproduction steps:
1. Download the attached user's project "KeyboardMinRepro.zip"
2. Build and Run on Oculus Quest 1/2
3. Wiggle the joystick, which causes the "KeyboardReproProjectActions MonoBehaviour" to call "TouchScreenKeyboard.Open()"
4. Notice that the debug info display reports that the newly-opened "TouchScreenKeyboard is state: Visible”, but the keyboard isn’t displaying in-headset
Expected result: TouchScreenKeyboard does not report the state "Visible" if the "oculus.software.overlay_keyboard" <uses-feature> is not defined in the AndroidManifest
Actual result: TouchScreenKeyboard reports state "Visible" even if the <uses-feature> is not defined in the AndroidManifest and thus the in-headset keyboard fails to instantiate
Reproduces on: Oculus XR 1.9.1 - 1.10.0 (2020.3.18f1, 2021.1.20f1, 2021.2.0b9, 2022.1.0a7)
Could not test 2019.4.30f1 due to the APP freezing after the Splash screen
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlasticSCM NullReferenceException on entering the Play Mode when Unity Version Control tab is added to the layout
- Shortcut Helper Bar does not appear when enabling it and disabling it
- "Property (urp_ReflProbes_BoxMin) exceeds previous array size" warning spams console after switching platforms
- Have to change Input Mapping Path twice for change to take effect when Auto-Save is enabled
- No Duplicate option is available when right clicking States in the Animator Window even though it's available via Shortcut
Add comment