|
Re: Build 100
Very interesting. I'll will try to pay attention to this. Thanks.
Benny
Very interesting. I'll will try to pay attention to this. Thanks.
Benny
|
By
Benny Barber
·
#1393
·
|
|
Re: Normal behavior?
Sorry, poor choice of words. What I should have said, is when I dismissed the keyboard to send the email...
Chuck
Sorry, poor choice of words. What I should have said, is when I dismissed the keyboard to send the email...
Chuck
|
By
Chuck Dean
·
#1392
·
|
|
Re: Normal behavior?
Thanks. What do you mean exactly when you say "When I came back"?
Thanks. What do you mean exactly when you say "When I came back"?
|
By
FlickType
·
#1391
·
|
|
Re: Normal behavior?
By the way,
I should mention that I have been typing quite a bit this afternoon since updating to build 100. I think I have answered about six or seven emails. I’m not sure if that could be the
By the way,
I should mention that I have been typing quite a bit this afternoon since updating to build 100. I think I have answered about six or seven emails. I’m not sure if that could be the
|
By
Chuck Dean
·
#1390
·
|
|
Re: Normal behavior?
Hello,
Yes, I restarted my iPhone after updating to build 100.
I am dictating this because when I was trying to write this reply, I capitalize the be in the word build, and then use the magic tap to
Hello,
Yes, I restarted my iPhone after updating to build 100.
I am dictating this because when I was trying to write this reply, I capitalize the be in the word build, and then use the magic tap to
|
By
Chuck Dean
·
#1389
·
|
|
Re: Build 100
Thank you Benny. I had briefly started work on the gesture issue before I had to switch back to text loss and crashing. One thing that I did find, which might not be the main thing but is worth
Thank you Benny. I had briefly started work on the gesture issue before I had to switch back to text loss and crashing. One thing that I did find, which might not be the main thing but is worth
|
By
FlickType
·
#1388
·
|
|
Re: Normal behavior?
Thanks Chuck. A few builds ago I made it so the screen would flash red whenever the keyboard gets a memory warning from iOS. I have since dropped the memory used by FlickType to well below the iOS
Thanks Chuck. A few builds ago I made it so the screen would flash red whenever the keyboard gets a memory warning from iOS. I have since dropped the memory used by FlickType to well below the iOS
|
By
FlickType
·
#1387
·
|
|
Re: Build 100
Kosta,
I know you are looking primarily for text loss and crashes, but I wanted to report the flick problem is still in 100. It is occurring while flicking through the alternative word list and
Kosta,
I know you are looking primarily for text loss and crashes, but I wanted to report the flick problem is still in 100. It is occurring while flicking through the alternative word list and
|
By
Benny Barber
·
#1386
·
|
|
Normal behavior?
Hello Kosta,
When typing a reply I typed the words App Store. After I two finger tapped to capitalize the words, the screen where the words are displayed turned red.
I noticed that it did not do
Hello Kosta,
When typing a reply I typed the words App Store. After I two finger tapped to capitalize the words, the screen where the words are displayed turned red.
I noticed that it did not do
|
By
Chuck Dean
·
#1385
·
|
|
Re: Losing text
OK👌
By
Chuck Dean
·
#1384
·
|
|
Losing text
Chuck, Benny, Macky and anyone else who has experience the lost text issue: Please make sure you install build 100 and reboot your device after updating.
If you experience the issue again, please
Chuck, Benny, Macky and anyone else who has experience the lost text issue: Please make sure you install build 100 and reboot your device after updating.
If you experience the issue again, please
|
By
FlickType
·
#1383
·
|
|
Build 100
We are releasing build 99 together with a minor internal change as build 100 to the wider beta group, in an effort to better understand the severity, nature, and frequency of the text loss issue. The
We are releasing build 99 together with a minor internal change as build 100 to the wider beta group, in an effort to better understand the severity, nature, and frequency of the text loss issue. The
|
By
FlickType
·
#1382
·
|
|
Re: Lost text build 99
The keyboard was still on screen and was not dismissed. I switched keyboards to see it my text was in my message and it was not. I canceled my message and sent you my message by starting completely
The keyboard was still on screen and was not dismissed. I switched keyboards to see it my text was in my message and it was not. I canceled my message and sent you my message by starting completely
|
By
Benny Barber
·
#1381
·
|
|
Re: Lost text build 99
Thank you Benny.
So as you were touch typing, which seems a common pattern with this issue, voiceover said "top of document" and did the keyboard get dismissed? Did you have to start editing again?
Thank you Benny.
So as you were touch typing, which seems a common pattern with this issue, voiceover said "top of document" and did the keyboard get dismissed? Did you have to start editing again?
|
By
FlickType
·
#1380
·
|
|
Re: Lost text build 99
Oh yeah. When the lost text occurred, voiceover said “top of document” and all the text was gone. I was touch typing when it happened.
Oh yeah. When the lost text occurred, voiceover said “top of document” and all the text was gone. I was touch typing when it happened.
|
By
Benny Barber
·
#1379
·
|
|
Re: Lost text build 99
Nothing with extension. The issue was in the custom keyboard. Thanks.
Benny
Nothing with extension. The issue was in the custom keyboard. Thanks.
Benny
|
By
Benny Barber
·
#1378
·
|
|
Re: Lost text build 99
Nothing starting with the word "Extension" either? And was that with the custom keyboard, or inside the container app?
Also, can you please describe exactly what you experienced when that happened?
Nothing starting with the word "Extension" either? And was that with the custom keyboard, or inside the container app?
Also, can you please describe exactly what you experienced when that happened?
|
By
FlickType
·
#1377
·
|
|
Re: Lost text build 99
Sorry to say there was no entries regarding FlickType. Thanks.
Benny
Sorry to say there was no entries regarding FlickType. Thanks.
Benny
|
By
Benny Barber
·
#1376
·
|
|
Re: Lost text build 99
Thank you Benny. Could you please follow these steps to send us your crash report directly?
You just go to your Settings app, then Privacy, Analytics, Analytics Data, find and open the relevant
Thank you Benny. Could you please follow these steps to send us your crash report directly?
You just go to your Settings app, then Privacy, Analytics, Analytics Data, find and open the relevant
|
By
FlickType
·
#1375
·
|
|
Lost text build 99
Time was 12:35 pm cdt on the 21st . Thanks.
Time was 12:35 pm cdt on the 21st . Thanks.
|
By
Benny Barber
·
#1374
·
|