Keyboard doesn’t open

@ItalianoDoc your stability report shows iOS did ask EFKey to open each time you tapped (about 15 times between 13:09 and 13:13), so it isn't a crash, the keyboard got opened but nothing ended up on screen. To see why, I need the diagnostics log: in the EFKey app go to the EF tab, turn on Diagnostics, open ChatGPT until the keyboard fails to show again, then come back and use Diagnostics → Records and export → Export everything and attach the file here.

@efko Hello, done, I’ll attach it. Loving your work😄

@ItalianoDoc thanks, glad you like it 😄 The log only caught one opening, at 13:35, because Diagnostics was switched on right before the export, and that opening looks normal. Did the keyboard show up at 13:35? If it did, please leave Diagnostics on, and the next time the keyboard doesn't appear, export right away and attach the new file. Mentioning the time it happened helps me find it in the log.

The keyboard opened at 13:35 when searching for the app in the search bar. I will attach a video so you can compare the time, and the new logs as you advised

@efko I’ll attach also another log

@ItalianoDoc the logs caught it. One part is a bug where the keys ended up below the visible keyboard when switching fields quickly, and that's fixed in 2.2, the next App Store update. The other part is iOS never putting EFKey on screen in ChatGPT (in your video EFKey wasn't even started), and I'm still looking into that one. Does it also happen outside ChatGPT, and does it go away after closing ChatGPT completely from the app switcher?

@efko Yes it happened also in other apps, but on chatGPT I managed to trigger it multiple times and yes if I force close and open again it starts working

@ItalianoDoc you now have TestFlight access, so please switch to build 440 there. It already has the fix for the keys ending up below the visible keyboard. The other part, iOS not showing the keyboard until you close the app, isn't fixed yet. If it happens on 440, leave Diagnostics on and attach a new export with the time it happened.

@efko Yes it is still happening. Time: 14:49

@ItalianoDoc your 14:49 export shows the empty keyboard from before is gone on 440, but four times in those minutes iOS started EFKey, connected your text field to it and then never put it on screen. Two other people get the same on iOS 27.0, so it's not only the 27.2 beta. 440 doesn't log enough about those moments yet; the next build, 441, will. Once you have it, one export right after it happens should tell me whether it's on iOS's side or mine.

@efko Ok perfect I’ll test it as soon as 441 will be live

@efko Here are two logs: the second one was at 21:14

@ItalianoDoc both exports were taken before EFKey wrote the line about the keyboard that didn't show, because 441 only writes it when the next keyboard opens. In build 442 it writes the line itself a few seconds after the failure, so export right after it happens and attach the file with the time.

@efko here it is, the time was about 00:37:50, let me know if you can see it

@ItalianoDoc this export caught it: six times between 00:10 and 00:36 iOS started EFKey and closed it again before it was ever shown, then ignored your taps for up to a few minutes. EFKey starts in under 70 ms every time, so I think it's the 27.2 beta. Could you install SwiftKey and try to trigger the same thing in ChatGPT the way you do with EFKey, to see if it gets stuck too? Build 442 will also log what's different about the times the keyboard does show.

@efko so I installed and tried it with SwiftKey and it gets stuck too

@ItalianoDoc if SwiftKey gets stuck the same way, it's iOS 27.2 beta not showing third-party keyboards it has already started, so there's nothing in EFKey I can fix for it. Please report it to Apple in the Feedback app (Keyboard, mention ChatGPT and that closing the app fixes it); I'm sending them the same. Until it's fixed, closing the app from the app switcher is the way out.