Forum Discussion
O.KENTO
2 years agoProtege
Keyboard Overlay Bug. Freeze and can not return App.
I faced a problem about Keyboard Overlay.
I tried using the system virtual keyboard but it doesn't stable.
The below step reproduces a fatal bug.
1. Set Require System Keyboard
2. Build app
3. Quickly pull a trigger two times.
It can not return to the app like the video.
Was there a mistake in my usage?
Version info
- Unity 2021.3.32f1
- Meta XR Core SDK 59.0.0
- Unity 2021.3.32f1
- Meta XR Core SDK 59.0.0
10 Replies
- flavobarthExplorer
I'm having the exact same issue. It seems to have started a week ago. Before that the keyboard worked as expected. Now it appears that sometimes it works, sometimes it doesn't sporadically.
I thought I was doing something wrong, but after three days of intensive testing, I'm starting to believe that this might be an issue with the Quest OS itself. You posting this here backens my suspicions.
- O.KENTOProtege
Thank you for your reply.
But, what should we do? Is the way to solve only waiting for update?
- flavobarthExplorer
I don't know. Hopefully they will fix it. In the meantime, if I find a solution I'll post it here.
- yoann.appertureExplorer
Omg, I was starting to get crazy with this bug, and seeing someone reporting the same issue is at least giving me hope that a fix can be found...
I'm also on Unity 2021.3.33f1
But using "Oculus XR Plugin 3.3.0"- O.KENTOProtege
Maybe, SDK or Plugin version does not affect this problem.
Cause I don't include them in my project.
I just added below code at AndroidManifest.
<uses-feature android:name="oculus.software.overlay_keyboard" android:required="false"/>- yoann.appertureExplorer
Yes I spend Monday and Tuesday switching aroung Unity version and SDK version and it didn't seems to accomplish much
- yoann.appertureExplorer
It seems that I found a fix !
Well kinda
It appears that the last Quest Update **bleep**ed the TMP Input Field with a content type "custom"
My Input field was with a custom type and a custom validator (cf screenshot)By changing it to "Standard" it's now working without no apparent issue (cf 2nd screenshot)
- flavobarthExplorer
Unfortunately, mine was already set as Standard and the issue persists.
I found that by changing the Line Type to Singeline make it work sometimes, while in Multiline it never works. Still, not even close to a fix.
As others have mentioned here, this is very likely an issue with a Quest update.
- yoann.appertureExplorer
That's a shame it didn't work for you π
It's for sure an issue caused by a Quest update, for us the bug is retroactif on previous build of the app that worked fine before !
Hope you find a workaround for your specific situation, and let's hope the issue is quickly fixed by Meta and/or Unity
- O.KENTOProtegeMaybe Updating OS fixed this issue. But I noticed new issue.InputField has the parameter named LineType.If it is set other than SingleLine and I select the Enter Button, then disappear virtual keyboard and appear it again.
Quick Links
- Horizon Developer Support
- Quest User Forums
- Troubleshooting Forum for problems with a game or app
- Quest Support for problems with your device
Other Meta Support
Related Content
- 5 years ago
- 8 months ago
- 2 years ago