Keyboard Overlay broken with v33 update

Same issue in the newly released v34 on Unreal (Oculus 4.27 fork - latest version). It works once, and then you can never show it again. Doesn't even work after you restart the app - You have to restart the whole device, so I'm guessing it's related to some keyboard service running in the background?

Hey there! The fix will be introduced in v35. Thanks! 

I'm shocked that no one has made a bigger issue of this yet. There are a lot of productivity apps that cannot function normally without the use of the keyboard. I'm not connected enough to light a fire under anyone but in my honest opinion this is a major failure for this to be an issue for as long as it has. Even if it isn't possible somehow to hot fix this I would expect an emergency operating system update for it.

Can anyone from oculus chime in on this and set some realistic expectations?

I just got update v35 and it is still not working. When clicking on a Unity input box sometimes the keyboard will appear (mainly after a restart of the headset) but most of the time it will simply not make the keyboard appear. In cases the keyboard appears but after closing it the controllers won't reappear in the app again. Lots of issues causing big problems with clients for now almost two months.

Are there any requirements for minimum versions of unity used to build the app or the sdk? There was no communication about developers needing to do anything for this to be resolved after the update but we would happily release a new version if it meant fixing the problem.

Hey developers! If you're still affected by the keyboard issue after updating to v35, can you reply to this with a link to your app? Also, let us know what version of Unity + the integration version you are using. Thanks. 

Hey all - I just wanted to share a workaround one of our support engineers found: 

For Unity Engine, if you use this syntax:

keyboard = TouchScreenKeyboard.Open("", TouchScreenKeyboardType.Default);  

it'll work on Android mobile devices but not in the Oculus Quest.

However, if you use the syntax:

keyboard = TouchScreenKeyboard.Open("", TouchScreenKeyboardType.ASCIICapable); 

or: 

TouchScreenKeyboard.Open("", TouchScreenKeyboardType.PhonePad);

then it should work with the Quest. 

Please make sure your headset is updated to v35. Thank you!

Do you think you can update your Oculus SDK V34 in your current project? Also yes, It is working on Unity 2020.3 LTS version.

Make sure on your OVRCameraRig on Quest Features under General Tab, you enabled the Require System Keyboard.  https://developer.oculus.com/documentation/unity/unity-keyboard-overlay/

If you are not familiar with TouchScreenKeyboard, see the reference: 

https://docs.unity3d.com/ScriptReference/TouchScreenKeyboard.Open.html

For you to confirm that this code is working, try and test it on your android mobile devices. 

You can call the function when you select InputField. e.g. 
public void EnabledOverlayASCIICapable()
{

keyboard = TouchScreenKeyboard.Open("", TouchScreenKeyboardType.ASCIICapable);

}

Once you select the InputField/Button and trigger an event to call your Function. 

Test on your InputField, Add an Event Trigger or create a function that will call the function to enable your keyboard overlay when your InputField is .onSelect(); 

I made identical bare bones projects targeting both Android and Oculus Quest 2 that just tests the TouchScreenKeyboard.Open call without anything else in the scene. The only difference is the standard Unity camera vs OculusCameraRig. I can confirm that TouchScreenKeyboard.Open displays the keyboard as expected on Android, but not Oculus.

using UnityEngine;

public class KeyboardTest : MonoBehaviour
{
    TouchScreenKeyboard keyboard;
    private void Start()
    {
        keyboard = TouchScreenKeyboard.Open("Keyboard", TouchScreenKeyboardType.ASCIICapable);
    }
}

Unity 2020.3.10

Platform SDK 35.0

Version 35.0.0.117.341.334653283

Runtime Version 35.0.0.118.341.334652914

AndroidOculus Quest 2

Any news please? This is definitely not working as expected, I am seeing tests from Drod with the same results and we are getting grilled by clients and dont know how to escalate this any more