I have seen one keyboard cause an issue previously but I can’t remember the model it was a special accessibilty keyboard though so you would probably know already if you had one.
I don’t know what else needs to be disabled for it to work, possibly anything with “Touch” in it, It doesn’t look like the dev ticket has been picked up for this yet.
We released a fix in 1.36.0 that should address this, Can you try updating and if you have the same issue still let me know. The PR with the change is below if anyone is curious.
I can confirm that the issue has been solved. But I don’t know which version solved the problem since I’ve only checked right now, and I’m on 1.51.2. However, it seems solved.