David,

 

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.

 

Alan Lemly

 

From: hello@flicktype.groups.io [mailto:hello@flicktype.groups.io] On Behalf Of David Goldfield
Sent: Wednesday, October 30, 2019 5:00 PM
To: flicktype@groups.io
Subject: [FlickType] Annoying Bug With the "Next Keyboard" Button for Text Entry in iOS 13.2

 

Hello.

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?

 

 

--
David Goldfield, Assistive Technology Specialist JAWS Certified: 2019 WWW.David-Goldfield.Com

--
The following information is important for all members of the V iPhone list.
 
If you have any questions or concerns about the running of this list, or if you feel that a member's post is inappropriate, please contact the owners or moderators directly rather than posting on the list itself.
 
Your V iPhone list moderator is Mark Taylor. Mark can be reached at: mktay@.... Your list owner is Cara Quinn - you can reach Cara at caraquinn@...
 
The archives for this list can be searched at:
http://www.mail-archive.com/viphone@.../
---
You received this message because you are subscribed to the Google Groups "VIPhone" group.
To unsubscribe from this group and stop receiving emails from it, send an email to viphone+unsubscribe@....
To view this discussion on the web visit https://groups.google.com/d/msgid/viphone/MWHPR10MB1359ECDC02FDB858EA47EE17EE600%40MWHPR10MB1359.namprd10.prod.outlook.com.

Hello.

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?

--
The following information is important for all members of the V iPhone list.
 
If you have any questions or concerns about the running of this list, or if you feel that a member's post is inappropriate, please contact the owners or moderators directly rather than posting on the list itself.
 
Your V iPhone list moderator is Mark Taylor. Mark can be reached at: mktay@.... Your list owner is Cara Quinn - you can reach Cara at caraquinn@...
 
The archives for this list can be searched at:
http://www.mail-archive.com/viphone@.../
---
You received this message because you are subscribed to the Google Groups "VIPhone" group.
To unsubscribe from this group and stop receiving emails from it, send an email to viphone+unsubscribe@....
To view this discussion on the web visit https://groups.google.com/d/msgid/viphone/MWHPR10MB1359ECDC02FDB858EA47EE17EE600%40MWHPR10MB1359.namprd10.prod.outlook.com.

On Oct 29, 2019, at 1:08 AM, Corie Brown <corie@...> wrote:

I cannot get the app to work properly in iOS 13 despite having a subscription.

It functions properly if I use the notepad in the app, but the universal keyboard does not give lush audio feedback system wide and is therefore effectively useless.

I have tried uninstalling and we installing the app hot that has not helped.

Universal functionality is turned on.

Is this app still being supported?

Currently a paid subscription seems like a waste of money!

All info and advise welcome.

Thanks. Corie  

On Oct 29, 2019, at 1:08 AM, Corie Brown <corie@...> wrote:

I cannot get the app to work properly in iOS 13 despite having a subscription.

It functions properly if I use the notepad in the app, but the universal keyboard does not give lush audio feedback system wide and is therefore effectively useless.

I have tried uninstalling and we installing the app hot that has not helped.

Universal functionality is turned on.

Is this app still being supported?

Currently a paid subscription seems like a waste of money!

All info and advise welcome.

Thanks. Corie

Hello. I apologize if you have received this question many times from many users. I was disappointed to discover that I'm unable to use Flicktype as a third party keyboard under iOS 13 although typing with your app does provide expected feedback when inside the app. Is this something that you need to address or is it up to Apple to correct the issue?

--
David Goldfield, Assistive Technology Specialist JAWS Certified: 2019 WWW.David-Goldfield.Com

It's apparently fixed in 13.2. Guessing it's related to keyboard changes they made.

On 10/20/2019 3:38 PM, David Goldfield wrote:

Hello. I apologize if you have received this question many times from many users. I was disappointed to discover that I'm unable to use Flicktype as a third party keyboard under iOS 13 although typing with your app does provide expected feedback when inside the app. Is this something that you need to address or is it up to Apple to correct the issue?

--
David Goldfield, Assistive Technology Specialist JAWS Certified: 2019 WWW.David-Goldfield.Com

Hello. I apologize if you have received this question many times from many users. I was disappointed to discover that I'm unable to use Flicktype as a third party keyboard under iOS 13 although typing with your app does provide expected feedback when inside the app. Is this something that you need to address or is it up to Apple to correct the issue?

--
David Goldfield, Assistive Technology Specialist JAWS Certified: 2019 WWW.David-Goldfield.Com

On Oct 16, 2019, at 6:17 PM, Gordon <gordon@...> wrote:



We had beta 3 of 13.2 drop earlier today and flick type is working perfectly with that as well. So everything is looking good. I would think that 13.2 would be out by the end of the month since we're on beta 3 now and things seem to be coming along nicely.

On 10/16/2019 7:48 PM, Alan Lemly wrote:

Thanks for the comments. I believe I'll stick with iOS 12.4.1 until iOS 13.2 is officially released.

 

Alan Lemly

 

From: hello@flicktype.groups.io [mailto:hello@flicktype.groups.io] On Behalf Of Shawn Krasniuk via Groups.Io
Sent: Wednesday, October 16, 2019 12:31 PM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Any improvements with iOS 13.1.3 update and the FlickType keyboard?

 

I don't think you'll see anything until iOS 13.2 which is still in beta. You're welcome though to install the beta on your phone if you're that impatient for it.

 

Regards,
Shawn,
Sent from Sophia, the MacBook Air

Want to join my WhatsApp groups such as Echo Enthusiasts, Accessibility Matters or my new group, Mac Users And Newbies? Send me a private email with your contact information and I'll happily add you.

Facebook Username: Shawn Krasniuk
Twitter Handle: shawnk_aka_bbs
Skype username: bbstheblindrapper
Facetime: bbsshawn@...

On Oct 16, 2019, at 12:00 PM, Chuck Dean <cadean329@...> wrote:

 

Hello Allen,

I just updated to iOS 13.1.3.

No, Fliktype is still broken. I tried replying to this email and I still don’t get any voice feedback from Fliktype. I also tried it in a search field, and in my notes, and I am getting no voice feedback whatsoever.

 

Evidently, this is not the update we have been waiting for.  

 

Chuck  (mobile)

Pleez x cuze enny tie ping or spelin air ores.

 

Our 1972 Honda 600 Coupe

 

Our 1961 Vespa 400

On Oct 16, 2019, at 9:20 AM, Alan Lemly <walemly@...> wrote:



Hi List,

 

I'm curious whether those of you using FlickType and iOS 13.x have updated to yesterday's iOS 13.1.3 release and can comment on whether the previous issues with the FlickType keyboard, VoiceOver, and iOS 13 have been improved or resolved.

 

Thanks in advance for your comments.

 

Alan Lemly

 

Thanks for the comments. I believe I'll stick with iOS 12.4.1 until iOS 13.2 is officially released.

 

Alan Lemly

 

From: hello@flicktype.groups.io [mailto:hello@flicktype.groups.io] On Behalf Of Shawn Krasniuk via Groups.Io
Sent: Wednesday, October 16, 2019 12:31 PM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Any improvements with iOS 13.1.3 update and the FlickType keyboard?

 

I don't think you'll see anything until iOS 13.2 which is still in beta. You're welcome though to install the beta on your phone if you're that impatient for it.

 

Regards,
Shawn,
Sent from Sophia, the MacBook Air

Want to join my WhatsApp groups such as Echo Enthusiasts, Accessibility Matters or my new group, Mac Users And Newbies? Send me a private email with your contact information and I'll happily add you.

Facebook Username: Shawn Krasniuk
Twitter Handle: shawnk_aka_bbs
Skype username: bbstheblindrapper
Facetime: bbsshawn@...

On Oct 16, 2019, at 12:00 PM, Chuck Dean <cadean329@...> wrote:

 

Hello Allen,

I just updated to iOS 13.1.3.

No, Fliktype is still broken. I tried replying to this email and I still don’t get any voice feedback from Fliktype. I also tried it in a search field, and in my notes, and I am getting no voice feedback whatsoever.

 

Evidently, this is not the update we have been waiting for.  

 

Chuck  (mobile)

Pleez x cuze enny tie ping or spelin air ores.

 

Our 1972 Honda 600 Coupe

 

Our 1961 Vespa 400

On Oct 16, 2019, at 9:20 AM, Alan Lemly <walemly@...> wrote:



Hi List,

 

I'm curious whether those of you using FlickType and iOS 13.x have updated to yesterday's iOS 13.1.3 release and can comment on whether the previous issues with the FlickType keyboard, VoiceOver, and iOS 13 have been improved or resolved.

 

Thanks in advance for your comments.

 

Alan Lemly

 

On Oct 16, 2019, at 12:20 PM, Alan Lemly <walemly@...> wrote:



Hi List,

 

I'm curious whether those of you using FlickType and iOS 13.x have updated to yesterday's iOS 13.1.3 release and can comment on whether the previous issues with the FlickType keyboard, VoiceOver, and iOS 13 have been improved or resolved.

 

Thanks in advance for your comments.

 

Alan Lemly

On Oct 16, 2019, at 12:00 PM, Chuck Dean <cadean329@...> wrote:

Hello Allen,

I just updated to iOS 13.1.3.

No, Fliktype is still broken. I tried replying to this email and I still don’t get any voice feedback from Fliktype. I also tried it in a search field, and in my notes, and I am getting no voice feedback whatsoever.

Evidently, this is not the update we have been waiting for.  

Chuck  (mobile)

Pleez x cuze enny tie ping or spelin air ores.

Our 1972 Honda 600 Coupe

Our 1961 Vespa 400

On Oct 16, 2019, at 9:20 AM, Alan Lemly <walemly@...> wrote:



Hi List,

 

I'm curious whether those of you using FlickType and iOS 13.x have updated to yesterday's iOS 13.1.3 release and can comment on whether the previous issues with the FlickType keyboard, VoiceOver, and iOS 13 have been improved or resolved.

 

Thanks in advance for your comments.

 

Alan Lemly