Thank you all for the feedback. 

It seems that the act of updating a keyboard can sometimes make iOS behave unexpectedly and not always show the keyboard when it should. Perhaps rebooting any time you update or revert to a different build is a good habit to have. 

To support us while still testing, all you would have to do is download the app from the App Store at any time after we launch, and simply upgrade it. Then you can be using TestFlight builds while supporting us at the same time, smile.

Thank you!

Kosta  

On Jun 19, 2018, at 07:19, Chuck Dean <cadean329@...> wrote:

Hello, 

 I agree with Dave. I am also available to continue as a tester, but I would also like to be able to support the app. 

 Chuck 

On Jun 19, 2018, at 3:01 AM, David Nason <dnason@...> wrote:

So far so good for me with the keyboard itself. 

Though the bug I reported previously after changing a capital letter to a lower case letter still persists. 

 Re the upgrade side of it, when I select the upgrade button in the app, it does now tell me that I am already subscribed. Of course though that does mean I cannot test the process for carrying out the upgrade. 

 

 If you continue to want / need us testing after the app store release, I will be more than happy to continue doing so. 

 I will be more than happy to pay though, so if doing this, you might consider including a tip jar or something. 

 

 Dave 

 

On 19 Jun 2018, at 10:05, George Cham <George.cham@...> wrote:

Well, I hope I explained it ok. As I type, everything is going ok. Sometimes it will move to start a new sentence with a capital letter while I'm in the middle of typing.

Kind Regards,

George Cham

‘May the Lord bless you and protect you. May the Lord smile on you and be gracious to you. May the Lord show you his favor and give you his peace.’

Numbers 6:24-26

Get Outlook for iOS

---

From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of FlickType <hello@...>
Sent: Tuesday, June 19, 2018 6:59:49 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 95

 

Hi George,

I assume you meant to type "And it's now" instead of "And it's not"?

On your question about what happens after we launch on the App Store:
as long as you are running a build that was downloaded from
TestFlight, you will be fully upgraded automatically at no cost. The
upgrade does not apply if the app is downloaded from the App Store. To
maintain the free upgrade you will therefore need to be on a
TestFlight build. I remind you that App Store builds are no different
than TestFlight builds, and any build that was released to the App
Store will also be available on TestFlight for some time, to make sure
there's always a stable build you can revert to if needed.

- Kosta


On Tue, Jun 19, 2018 at 1:45 AM George Cham <George.cham@...> wrote:
>
> Hi costa and Ashley. The  Full features of the paid version are  working. As I type, FlickType Will disappear while typing. And its not allowing me to complete a word, or sentence. Just a question on the in app purchase. When the full    screen keyboard is launched in  the App Store, and I download it will beta testers be      charged?
>
> Kind Regards,
>
> George Cham
>
> ‘May the Lord bless you and protect you. May the Lord smile on you and be gracious to you. May the Lord show you his favor and give you his peace.’
> Numbers 6:24-26
> Get Outlook for iOS
> ________________________________
> From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of FlickType <hello@...>
> Sent: Tuesday, June 19, 2018 6:32:42 PM
> To: alpha@flicktype.groups.io
> Subject: [FlickType-alpha] Build 95
>
> - Set the actual launch price for the paid feature. We got you all worried there for a second, smile. Thank you for all your feedback on the pricing.
> - TestFlight users are now automatically upgraded to always have the full custom keyboard functionality.
> - Speculative fix for the crash that causes lost text. If the issue persists, please let us know what you were attempting to do at the precise moment the crash occurred, as well as the time that it occurred. Also a set of steps which reliably reproduce the issue would be incredibly helpful, as we have been unable to reproduce the issue so far.
>
> Thank you for testing!
>
> Warmly,
> Kosta & Ashley
>
>
>
>

On Jun 19, 2018, at 10:33 PM, FlickType <hello@flicktype.com> wrote:

What is the app that has the tip jar feature, or what it the feature
itself called?

Kosta
On Tue, Jun 19, 2018 at 5:25 PM Salman Haider
<salmanhaider.purdue@gmail.com> wrote:

Thank you Kosta. I can confirm that the tip jar option is definitely allowed as I do use at least one app that has that feature. It gives great flexibility in terms of contribution. Whether it's a monthly, annual or a one time contribution. So definitely something that you guys can consider.
Thanks.

On Jun 19, 2018, at 7:33 PM, FlickType <hello@flicktype.com> wrote:

Thank you Benny, build 88 is the suspect one on our end as well. While we're investigating, a couple things you could also try are updating to iOS 11.4, and trying the latest build on a different device if you happen to have one.

Thank you Salman for the pricing feedback. We will need to look into tip jar options and if those are allowed by Apple.

Kosta

On Jun 19, 2018, at 10:08 PM, FlickType <hello@flicktype.com> wrote:

- Fixed rare crash that caused loss of text

On Jun 19, 2018, at 9:56 PM, FlickType <hello@flicktype.com> wrote:

Thank you Chuck. I figured out the cause, and a new build with a fix
is coming shortly.

For anyone interested in the background, it appears that we are
running at the very limit of the tight memory allowance for iOS
keyboards. Some recent change made us cross the memory threshold ever
so slightly on some rare occasions, and iOS simply restarts the
keyboard whenever that happens.

The real fix for this is a complete rewrite of the word recognition
engine, something which is planned for the future and is an area I am
particularly excited about. But there is a lot of work before we get
there, so don't hold your breath just yet, smile.

Kosta

On Tue, Jun 19, 2018 at 9:36 PM Chuck Dean <cadean329@gmail.com> wrote:

Another vanishing text episode

Hi Kosta,
I was typing in my journal app at 9:31 PDT and only the last line of about 5 showed up. I wasn't doing anything unusual, and I did nut notice a flash this time.
Chuck

Another vanishing text episode

Hi Kosta,
I was typing in my journal app at 9:31 PDT and only the last line of about 5 showed up. I wasn't doing anything unusual, and I did nut notice a flash this time.
Chuck

On Jun 19, 2018, at 5:57 PM, FlickType <hello@flicktype.com> wrote:

Thank you Chuck. Can you please confirm if it was 4:34 or 5:34 PDT?
I'm asking because I see an indication of a crash around 5:34 PDT, in
other words about 25 minutes ago.

- Kosta

On Tue, Jun 19, 2018 at 5:45 PM Chuck Dean <cadean329@gmail.com> wrote:

Text disappeared (
Hi Kosta,
I was typing an email on my iPhone 8 with the latest iOS. I was going to type the words app store, and when I went to capitalize the A, the screen flashed twice and all the text I had typed disappeared.

This happened at 4:34 PDT
BTW, I was using the 3D touch to capitalize and was using the latest update of the custom keyboard.
Chuck iyou

Text disappeared (
Hi Kosta,
I was typing an email on my iPhone 8 with the latest iOS. I was going to type the words app store, and when I went to capitalize the A, the screen flashed twice and all the text I had typed disappeared.

This happened at 4:34 PDT
BTW, I was using the 3D touch to capitalize and was using the latest update of the custom keyboard.
Chuck iyou

On Jun 19, 2018, at 5:56 PM, FlickType <hello@flicktype.com> wrote:

Thanks Benny, although I'm a little confused. You also mentioned that build 88 had the problem as well, so that would be the earliest build that had the issue?

- Kosta

On Jun 19, 2018, at 5:56 PM, FlickType <hello@flicktype.com> wrote:

Thanks Benny, although I'm a little confused. You also mentioned that build 88 had the problem as well, so that would be the earliest build that had the issue?

- Kosta

On Jun 19, 2018, at 2:31 PM, FlickType <hello@flicktype.com> wrote:

Thanks.

Benny, could you please confirm if build 88 had the same issue? I know it’s a broken build that keeps popping us alerts, but if your issue happens very often, it should be easy to check and that would help a lot.

Kosta

On Jun 19, 2018, at 12:23, Benny Barber <rebelben@bellsouth.net> wrote:

Kosta,
This is the first build that I have had this flicking problem. Thanks.

On Jun 19, 2018, at 3:32 AM, FlickType <hello@flicktype.com> wrote:

- Set the actual launch price for the paid feature. We got you all worried there for a second, smile. Thank you for all your feedback on the pricing.
- TestFlight users are now automatically upgraded to always have the full custom keyboard functionality.
- Speculative fix for the crash that causes lost text. If the issue persists, please let us know what you were attempting to do at the precise moment the crash occurred, as well as the time that it occurred. Also a set of steps which reliably reproduce the issue would be incredibly helpful, as we have been unable to reproduce the issue so far.

Thank you for testing!

Warmly,
Kosta & Ashley

On Jun 19, 2018, at 2:31 PM, FlickType <hello@flicktype.com> wrote:

Thanks.

Benny, could you please confirm if build 88 had the same issue? I know it’s a broken build that keeps popping us alerts, but if your issue happens very often, it should be easy to check and that would help a lot.

Kosta

On Jun 19, 2018, at 12:23, Benny Barber <rebelben@bellsouth.net> wrote:

Kosta,
This is the first build that I have had this flicking problem. Thanks.

On Jun 19, 2018, at 3:32 AM, FlickType <hello@flicktype.com> wrote:

- Set the actual launch price for the paid feature. We got you all worried there for a second, smile. Thank you for all your feedback on the pricing.
- TestFlight users are now automatically upgraded to always have the full custom keyboard functionality.
- Speculative fix for the crash that causes lost text. If the issue persists, please let us know what you were attempting to do at the precise moment the crash occurred, as well as the time that it occurred. Also a set of steps which reliably reproduce the issue would be incredibly helpful, as we have been unable to reproduce the issue so far.

Thank you for testing!

Warmly,
Kosta & Ashley