Search Issue Tracker
Fixed
Fixed in 1.12.0
Votes
0
Found in [Package]
1.12.0
Issue ID
OXPB-31
Regression
No
[Oculus] Quest 2 does not gain focus when user closes system keyboard with Oculus Home button
dReproduction steps:
1. Open the attached user's project "ScrollRectTest.zip"
2. Build the project for Quest 1/2 and start the application
3. Point controller beam to the input field and press trigger. Observe system keyboard appearing
4. Point controller to blue "confirm" button on the keyboard. Observe system keyboard closing, and controllers are being tracked
5. Repeat step 3
6. Press Oculus Home button on the right controller
Expected result: Observe system keyboard closing. Controllers are tracked and functional
Actual result: Controllers are not tracked and the app became not functional, pressing the Home button again closes the application (See attached Issue.mp4)
Reproduces on: 2020.3.33f1, 2021.2.18f1, 2022.1.0b16, 2022.2.0a10
Could not test on 2019.4.38f1 due to downgrade errors
Notes:
-Issue reproduces with both Open XR and Oculus XR plugins
-You can refer to "test.cs" file with some status check code. After step 6 TouchScreenKeyboard.visible is still 'true', also custom plugin KeyboardChecker.java shows that keyboard status is opened (see native plugin code attached "KeyboardChecker.java")
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
- Getting a deprecated package for JetBrains Rider pop up when opening or creating a project
- [Android] Volume level of the same audio file is different on Samsung Galaxy Tab A8 between 2023.3.0b3 and 2023.3.0b4
- ‘Expected end of value’ warning occurs when a property declaration includes five or more variable references
- Crash on BurstCompilerService::CompileAsync when entering Play mode in a specific scene
- InvalidOperationException when using Game Camera Preview in Scene window with a custom RenderGraph pass
Resolution Note (fix version 1.12.0):
Looks like the parent issue was closed, but this port wasn't.