Date   

Re: Build 100

Benny Barber
 

Very interesting. I'll will try to pay attention to this. Thanks.
Benny

On Jun 21, 2018, at 7:15 PM, FlickType <@FlickType> wrote:

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 noting, is that if you flick somewhat diagonally instead of vertically or horizontally, the flick might not register and you will get the touch typing exploration gesture to kick in. I'll have to check if this is something that only started happening recently, and I'd love to know if this knowledge makes a difference for you when you next use the current build.

Kosta



Re: Normal behavior?

Chuck Dean
 


Sorry, poor choice of words. What I should have said, is when I dismissed the keyboard to send the email... 
 Chuck 

On Jun 21, 2018, at 5:18 PM, FlickType <hello@...> wrote:

Thanks. What do you mean exactly when you say "When I came back"?

On Thu, Jun 21, 2018 at 5:16 PM Chuck Dean <cadean329@...> wrote:
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 go to numbers to type in 100. When I came back to send, my text was missing.
Chuck

> On Jun 21, 2018, at 5:10 PM, FlickType <hello@...> wrote:
>
> 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 threshold, so the fact that you are still getting those is very unexpected. In our analytics, I am currently only seeing 2 devices that are triggering memory warnings, among hundreds that are not. Have you restarted your device recently? There must be something quite unusual with your configuration or device, although I cannot say what.
>
> Kosta
>
>
>
>




Re: Normal behavior?

 

Thanks. What do you mean exactly when you say "When I came back"?


On Thu, Jun 21, 2018 at 5:16 PM Chuck Dean <cadean329@...> wrote:
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 go to numbers to type in 100. When I came back to send, my text was missing.
Chuck

> On Jun 21, 2018, at 5:10 PM, FlickType <hello@...> wrote:
>
> 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 threshold, so the fact that you are still getting those is very unexpected. In our analytics, I am currently only seeing 2 devices that are triggering memory warnings, among hundreds that are not. Have you restarted your device recently? There must be something quite unusual with your configuration or device, although I cannot say what.
>
> Kosta
>
>
>
>




Re: Normal behavior?

Chuck Dean
 

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 reason why I am getting to the upper limit of the memory.
Chuck

On Jun 21, 2018, at 5:16 PM, Chuck Dean <cadean329@...> wrote:

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 go to numbers to type in 100. When I came back to send, my text was missing.
Chuck

On Jun 21, 2018, at 5:10 PM, FlickType <@FlickType> wrote:

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 threshold, so the fact that you are still getting those is very unexpected. In our analytics, I am currently only seeing 2 devices that are triggering memory warnings, among hundreds that are not. Have you restarted your device recently? There must be something quite unusual with your configuration or device, although I cannot say what.

Kosta





Re: Normal behavior?

Chuck Dean
 

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 go to numbers to type in 100. When I came back to send, my text was missing.
Chuck

On Jun 21, 2018, at 5:10 PM, FlickType <@FlickType> wrote:

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 threshold, so the fact that you are still getting those is very unexpected. In our analytics, I am currently only seeing 2 devices that are triggering memory warnings, among hundreds that are not. Have you restarted your device recently? There must be something quite unusual with your configuration or device, although I cannot say what.

Kosta




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 noting, is that if you flick somewhat diagonally instead of vertically or horizontally, the flick might not register and you will get the touch typing exploration gesture to kick in. I'll have to check if this is something that only started happening recently, and I'd love to know if this knowledge makes a difference for you when you next use the current build.

Kosta


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 threshold, so the fact that you are still getting those is very unexpected. In our analytics, I am currently only seeing 2 devices that are triggering memory warnings, among hundreds that are not. Have you restarted your device recently? There must be something quite unusual with your configuration or device, although I cannot say what.

Kosta


Re: Build 100

Benny Barber
 

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 while flicking word by word with the 2 finger flick right and left. I'm still testing for text loss. Thanks.
Benny

On Jun 21, 2018, at 5:30 PM, FlickType <@FlickType> wrote:

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 release notes follow below:

Please restart your device after updating FlickType, and send all your feedback to beta@flicktype.groups.io.

What's new in this version:
- Bug fixes and stability improvements. Please let us know if you experience any crashes or text loss. Fixing such issues is a top priority for us.
- Updated "Welcome" tab with more streamlined instructions. Tell us what you think, and if we missed anything!
- Added new "Upgrade" tab for the paid custom keyboard feature. TestFlight users are automatically upgraded to always have the full custom keyboard functionality.
- The custom keyboard will now work without "Full Access", but it won't be able to play sound effects and will only have minimal touch typing functionality without flick gestures or tap typing.
- Increased maximum emoji shortcuts from 6 to 10.

Thank you for testing FlickType!

Warmly,
Kosta and Ashley



Normal behavior?

Chuck Dean
 

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 it when I typed the same words in this email.

I remember a few days ago, when I lost text, the screen also turned red when I capitalized letters.
No text loss yet.😎
Chuck


Re: Losing text

Chuck Dean
 

OK👌

On Jun 21, 2018, at 4:42 PM, FlickType <@FlickType> wrote:

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 describe in as much detail the very first indication you got that something was wrong, in addition to what you where doing at that precise moment. For example, any unexpected sound or visual indication, or any other unusual behavior. And if you were typing manually, please let us know if something unexpected happened as you were touching down, moving, or releasing your finger from the screen.

Thanks,
Kosta



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 describe in as much detail the very first indication you got that something was wrong, in addition to what you where doing at that precise moment. For example, any unexpected sound or visual indication, or any other unusual behavior. And if you were typing manually, please let us know if something unexpected happened as you were touching down, moving, or releasing your finger from the screen.

Thanks,
Kosta


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 release notes follow below:

Please restart your device after updating FlickType, and send all your feedback to beta@flicktype.groups.io.

What's new in this version:
- Bug fixes and stability improvements. Please let us know if you experience any crashes or text loss. Fixing such issues is a top priority for us.
- Updated "Welcome" tab with more streamlined instructions. Tell us what you think, and if we missed anything!
- Added new "Upgrade" tab for the paid custom keyboard feature. TestFlight users are automatically upgraded to always have the full custom keyboard functionality.
- The custom keyboard will now work without "Full Access", but it won't be able to play sound effects and will only have minimal touch typing functionality without flick gestures or tap typing.
- Increased maximum emoji shortcuts from 6 to 10.

Thank you for testing FlickType!

Warmly,
Kosta and Ashley


Re: Lost text build 99

Benny Barber
 

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 over. I wish I had more. Thanks
Benny

On Jun 21, 2018, at 2:26 PM, FlickType <@FlickType> wrote:

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? Or did you have to switch keyboards again? I'm trying to understand if the keyboard gets killed, or if it stays on screen but somehow the text gets lost.

Thanks,
Kosta



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? Or did you have to switch keyboards again? I'm trying to understand if the keyboard gets killed, or if it stays on screen but somehow the text gets lost.

Thanks,
Kosta


Re: Lost text build 99

Benny Barber
 

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.

On Jun 21, 2018, at 1:39 PM, FlickType <hello@...> wrote:

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? Did the keyboard sound like it went away or anything like that?

Thanks,
Kosta




On Thu, Jun 21, 2018 at 11:25 AM Benny Barber <rebelben@...> wrote:
Sorry to say there was no entries regarding FlickType.  Thanks.

Benny

> On Jun 21, 2018, at 12:58 PM, FlickType <hello@...> wrote:
>
> 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 FlickType entry, and then share using the button at the top. All FlickType custom keyboard entries will start with the word "Extension", followed by a date and time.
>
> Thanks,
> Kosta
>
>
>





Re: Lost text build 99

Benny Barber
 

Nothing with extension.  The issue was in the custom keyboard.  Thanks.
Benny

On Jun 21, 2018, at 1:39 PM, FlickType <hello@...> wrote:

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? Did the keyboard sound like it went away or anything like that?

Thanks,
Kosta




On Thu, Jun 21, 2018 at 11:25 AM Benny Barber <rebelben@...> wrote:
Sorry to say there was no entries regarding FlickType.  Thanks.

Benny

> On Jun 21, 2018, at 12:58 PM, FlickType <hello@...> wrote:
>
> 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 FlickType entry, and then share using the button at the top. All FlickType custom keyboard entries will start with the word "Extension", followed by a date and time.
>
> Thanks,
> Kosta
>
>
>





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? Did the keyboard sound like it went away or anything like that?

Thanks,
Kosta




On Thu, Jun 21, 2018 at 11:25 AM Benny Barber <rebelben@...> wrote:
Sorry to say there was no entries regarding FlickType.  Thanks.

Benny

> On Jun 21, 2018, at 12:58 PM, FlickType <hello@...> wrote:
>
> 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 FlickType entry, and then share using the button at the top. All FlickType custom keyboard entries will start with the word "Extension", followed by a date and time.
>
> Thanks,
> Kosta
>
>
>





Re: Lost text build 99

Benny Barber
 

Sorry to say there was no entries regarding FlickType. Thanks.

Benny

On Jun 21, 2018, at 12:58 PM, FlickType <@FlickType> wrote:

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 FlickType entry, and then share using the button at the top. All FlickType custom keyboard entries will start with the word "Extension", followed by a date and time.

Thanks,
Kosta



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 FlickType entry, and then share using the button at the top. All FlickType custom keyboard entries will start with the word "Extension", followed by a date and time.

Thanks,
Kosta


Lost text build 99

Benny Barber
 

Time was 12:35 pm cdt on the 21st . Thanks.