Re: Annoying Bug With the "Next Keyboard" Button for Text Entry in iOS 13.2
toggle quoted messageShow quoted text
My iPhone 8 running iOS 13.2 is doing exactly as you described but my understanding is that behavior is expected. When I'm in an edit field and my next keyboard says something other than what I want, I double tap and hold it and slide up until I hear FlickType. When I release, I'm ready to input with FlickType. If you simply double tap when the next keyboard key has focus and is listing a keyboard other than the one you want, the expected behavior is for it to launch that keyboard. I'm finding that with iOS 13.2, FlickType seems to be sticking better to the next keyboard button than it did in iOS 12.4.1 so I have no complaints.
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of David Goldfield
Sent: Wednesday, October 30, 2019 5:00 PM
Subject: [FlickType] Annoying Bug With the "Next Keyboard" Button for Text Entry in iOS 13.2
On the positive side I am thrilled that Flicktype's functionality has been restored to VoiceOver users as a third party keyboard in iOS 13.2. However, there is an annoying issue on my iPhone 8 which I have discovered that I wanted to mention. I plan to email Apple Accessibility about this but if others are affected by this issue I'd like to encourage them to do so as well.
When I bring up a text entry field with the standard English keyboard the "next keyboard" button reports something like "next keyboard, emoji." Double tapping this button switches to the emoji keyboard, as expected. I then hear "next keyboard, Flicktype" but double tapping the button does not switch to the Flicktype keyboard as it should and is it reliably did in iOS 12. Instead, it stays on the emoji keyboard. As a workaround if I double tap and hold the button it does seem to switch over to using Flicktype. I'm wondering if other Flicktype users are able to confirm this?