It’s hard to fix something if it can’t be reproduced or if there is no known way to reproduce the problem. Unfortunately code doesn’t have giant arrows pointing to errors. This is the type of battle I face every day at my job.
I’m less inclined to thing that it’s a glide issue and more of an iOS issue that may or may not be caused by some sort of glide configuration. However, this doesn’t happen for everyone, so maybe we need to find some common patterns that would cause this to happen for certain people.
For anybody that has this issue, what are your regional settings for the OS, the Browser, and the Keyboard? I feel like I’ve seen this complaint more often from Hebrew speaking users compare to other languages. Could it be some sort of incompatibly with RTL languages? Could it be an incompatibility with certain regions? Could it be certain types of keyboard layouts that don’t work with different regional settings?
It’s hard to say what’s happening. I don’t have an iPhone, so I am unable to test anything myself. But I think everyone with the issue needs to chime in with any information that could help surface any patterns that would cause this issue to occur.
I suggest reporting any phone models, iOS versions, browser versions, keyboard versions, any regional settings, any use of third party keyboards. Is Bluetooth on? Has anybody ever connect a Bluetooth keyboard to their device?
I’ve done several Google searches for missing keyboard issues. It seems like it does happen outside of glide, but doesn’t appear to be a widespread issue. (Personally, I’d say dump iPhone because apple seems to cause a lot of issues for people…joking )
Can anyone with the issue do a Google search and see if any of these issues or solutions seem to help, or at least trigger any ideas for things to check. Most of what I’ve read seems to be resolved by restarting the device or turning off Bluetooth. That’s all I’ve really found so far.
If we can help glide formulate a pattern for when this keyboard issue occurs, then it will make it easier for them to find the cause of the issue. I’ve been on that end of the development process. Enough information from an end user can mean the difference of mere hours to find and fix a problem versus months of research. I’ve spent weeks and months…even years trying to track down a coding issue and in the end it’s usually a couple of characters or one line of code. Reliably reproducing the problem is always the first step. Then it’s understanding how the code should change and what are any possible consequences of that change. After that it’s smooth sailing.