Topics

Build 132 now it's working


Chuck Dean
 

Hello Kosta,
I reinstalled and restarted my iPhone and now build 132 is acting as expected. Something must have gone wrong with the first install because nothing would happen if I tapped above the keyboard. BTW I had the same thing happen while typing this reply the first time so I restarted the iPhone. This happened when I tried using the three finger hole to hear what I had typed, but I think one of my fingers was above the keyboard.
If this is working as expected, its pretty cool... Being able to interact with all fields and send buttons.๐Ÿ˜Ž

Good job!๐Ÿ‘

Chuck


 

Thank you Chuck.

Just to confirm, was it restarting your device that seems to have fixed the issue, or did reinstalling initially helped to some extent? And did you initially restart your device after upgrading to 132, or did you only do so after experiencing the issue?

Weโ€™re trying to identify what are the minimum and easiest steps that weโ€™d recommend to other users if they have similar issues. So far weโ€™ve found that restarting the device, even though a bit drastic, might be the simplest measure to combat all sorts of unexpected behavior.

Also, what iOS version are you currently running?

Thanks,
Kosta

On Jul 5, 2018, at 15:53, Chuck Dean <cadean329@...> wrote:


Hello Kosta,
I reinstalled and restarted my iPhone and now build 132 is acting as expected. Something must have gone wrong with the first install because nothing would happen if I tapped above the keyboard. BTW I had the same thing happen while typing this reply the first time so I restarted the iPhone. This happened when I tried using the three finger hole to hear what I had typed, but I think one of my fingers was above the keyboard.
If this is working as expected, its pretty cool... Being able to interact with all fields and send buttons.๐Ÿ˜Ž

Good job!๐Ÿ‘

Chuck


Chuck Dean
 

I am using an iPhone ate running Version, iOS 11.4

I think it was the restart of the iPhone that cured the problem.

I just found a problem. As I was typing the first draft of this reply, I accidentally touched the screen above the FlickType keyboard and all my text was lost. I am being careful to stay within the borders of the keyboard this time. This could be a big problem for those with less vision.
Chuck
I am dictating this part of the message. When I went to send, no text showed up on this particular email, I dismiss the screen, and then text showed up.
I then change the iOS keyboard so I could use dictation to finish this email.

On Jul 5, 2018, at 4:07 PM, FlickType <@FlickType> wrote:

Thank you Chuck.

Just to confirm, was it restarting your device that seems to have fixed the issue, or did reinstalling initially helped to some extent? And did you initially restart your device after upgrading to 132, or did you only do so after experiencing the issue?

Weโ€™re trying to identify what are the minimum and easiest steps that weโ€™d recommend to other users if they have similar issues. So far weโ€™ve found that restarting the device, even though a bit drastic, might be the simplest measure to combat all sorts of unexpected behavior.

Also, what iOS version are you currently running?

Thanks,
Kosta

On Jul 5, 2018, at 15:53, Chuck Dean <cadean329@...> wrote:


Hello Kosta,
I reinstalled and restarted my iPhone and now build 132 is acting as expected. Something must have gone wrong with the first install because nothing would happen if I tapped above the keyboard. BTW I had the same thing happen while typing this reply the first time so I restarted the iPhone. This happened when I tried using the three finger hole to hear what I had typed, but I think one of my fingers was above the keyboard.
If this is working as expected, its pretty cool... Being able to interact with all fields and send buttons.๐Ÿ˜Ž

Good job!๐Ÿ‘

Chuck