Skip to main content
OKENTO
Up and Coming
December 18, 2023

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

10 replies

Inspiring
December 19, 2023

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.

 

OKENTO
OKENTOAuthor
Up and Coming
December 19, 2023

Thank you for your reply.

But, what should we do? Is the way to solve only waiting for update?

Inspiring
December 19, 2023

I don't know. Hopefully they will fix it. In the meantime, if I find a solution I'll post it here.

yoannapperture
New Participant
December 20, 2023

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"

OKENTO
OKENTOAuthor
Up and Coming
December 20, 2023

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"/>

yoannapperture
New Participant
December 20, 2023

Yes I spend Monday and Tuesday switching aroung Unity version and SDK version and it didn't seems to accomplish much

yoannapperture
New Participant
December 20, 2023

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)

 

Inspiring
December 20, 2023

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.

 

yoannapperture
New Participant
December 20, 2023

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

OKENTO
OKENTOAuthor
Up and Coming
January 6, 2024
Maybe 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.