Keyboard Overlay broken with v33 update

Alright, so it seems that this is at least partially an issue with the version of Unity (2020.3.10) we were using. I checked the release notes and there are several changes and fixes related to TouchScreenKeyboard between 2020.3.15 and 2020.3.20. We updated to the latest LTS version (2020.3.25) and the keyboard is now working as expected.

Thanks to everyone for the support, especially DanRaySN for some helpful back-and-forth. 

Whereas now it works much better and seems functional most of the time there are still issues where the app doesn't return input back to the app and you are left with dummy controllers after the keyboard is closed, as some other users have indicated and similar issues to this other topic https://forums.oculusvr.com/t5/Unity-VR-Development/Issues-with-the-Keyboard-overlay/td-p/877789/page/2

I still have that problem. I'm using Oculus Integration v35, and am on 2020.3.25. 

Calling in the OnSelect event

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

didn't make the keyboard appear either, even though the OnSelect function of the input field is called.

My Quest 2 is in v35. I am also using the XR Toolkit.

Has anyone found another workaround ? 

Come on Oculus I can't believe this is still an issue.

I still have the issue with Oculus Integration v37, Unity 2020.1.17f1 that basically everything works except if you use the blue keyboard button, the "InputFocusAquired" is never invoked thus having to manually exit to menu and go back to the app.

Just tried this in v38, same thing though this time now my in-game controllers freeze in the background while typing

It seems Unity 2021.3.2 has a fix related to Quest software keyboard (I haven't tried it yet though).
> XR: Fixed Oculus Quest software keyboard not showing up on InputField interaction. (1417991)

It appears that Unity version 2021.3.2 and Oculus Integration version V40 has partially fixed the keyboard issue. I am now able to open and close a keyboard by selecting a text input field and pressing enter.

However, manually opening the keyboard via the following is STILL broken. 

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

Anyone developing on quest these days is using an updated version meaning the current docs will lead them to a broken result. The oculus team need to fix this or update the docs with this information so more people don't waste their time.