Date   

Re: Build 116

 

We received a crash for this build, from someone in Australia on an iPad at about 9:25 pm Australia time. Could you please let us know if you noticed this, and if there was any text loss or other unexpected behavior?

Thank you,
Kosta


Re: Build 116

Chuck Dean
 

Hi Kosta,
Build 116 is working well. I tried it in what seems to be my most problematic app, my journal. The prediction is better, and no red screens or crashes.👍


I only typed a paragraph so I'll have to do more testing tomorrow.

Chuck ,

On Jun 28, 2018, at 11:44 PM, FlickType <@FlickType> wrote:

- Crash / stability fixes. Please test for lost or duplicate text.
- Possible fix for a subscription issue.




Re: Accuracy poll #poll

Chuck Dean
 


In build 114, it seemed to be much worse than builds before and after. Right now, it is working well. 
 Chuck 

On Jun 28, 2018, at 11:53 PM, FlickType <hello@...> wrote:

A new poll has been created:

Has the accuracy changed since build 110 or so?

1. Yes
2. No
3. Hard to tell, there's always some misses

Vote Now


Accuracy poll #poll

 

Has the accuracy changed since build 110 or so?

Results

See Who Responded


Build 116

 

- Crash / stability fixes. Please test for lost or duplicate text.
- Possible fix for a subscription issue.


Re: Build 115 problems

 

Thank you George, I got your report as well.

I am investigating red screens and crashes. Might have a new build out in an hour or so.

Thanks,
Kosta


Re: Build 115 problems

George Cham
 

Hello costa, I sent the crash report to hello @ FlickType. Com.
Just as I started to type. I changed keyboards from iOS to FlickType.
Just as I was about to type, I was in the keyboard and I had not typed anything.
I got the red screen even tho nothing had been typed.

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 Chuck Dean <cadean329@...>
Sent: Friday, June 29, 2018 3:15:06 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 115 problems
 

 Ok, I'll make a new contact with the direct email.
 
 I hope you enjoy investigating these problems. It would drive me crazy.😎

> On Jun 28, 2018, at 10:12 PM, FlickType <hello@...> wrote:
>
> Thank you Chuck, I got them and I'm investigating. FYI you sent them
> to the group email rather than the hello@..., but they were
> pending moderation.
>
> Kosta
>
>
>
>> On Thu, Jun 28, 2018 at 9:52 PM Chuck Dean <cadean329@...> wrote:
>>
>> Hi,
>> My mistake, there were only four crash reports for today. I sent them.
>> Chuck
>>
>>> On Jun 28, 2018, at 9:45 PM, FlickType <hello@...> wrote:
>>>
>>> Thank you Chuck. Once you open a crash report, there is a share button
>>> at the top right of the screen. It would be great if you could send
>>> all 5 to hello@....
>>>
>>> George, sounds like both you and Chuck had some issue while trying to
>>> manually type the letter A. Could you please also check to see if you
>>> have any FlickType crash logs from the last couple of days?
>>>
>>> Below are steps to share a crash report from your iPhone:
>>> 1. Go to the iOS Settings app.
>>> 2. Go to Privacy.
>>> 3. Go to Analytics or Diagnostics & Usage.
>>> 4. Select Analytics Data or Diagnostics & Usage Data.
>>>
>>> Thank you,
>>> Kosta
>>>
>>>
>>>
>>
>>
>>
>
>
>




Re: Build 115 problems

Chuck Dean
 

Ok, I'll make a new contact with the direct email.

I hope you enjoy investigating these problems. It would drive me crazy.😎

On Jun 28, 2018, at 10:12 PM, FlickType <@FlickType> wrote:

Thank you Chuck, I got them and I'm investigating. FYI you sent them
to the group email rather than the @FlickType, but they were
pending moderation.

Kosta



On Thu, Jun 28, 2018 at 9:52 PM Chuck Dean <cadean329@...> wrote:

Hi,
My mistake, there were only four crash reports for today. I sent them.
Chuck

On Jun 28, 2018, at 9:45 PM, FlickType <@FlickType> wrote:

Thank you Chuck. Once you open a crash report, there is a share button
at the top right of the screen. It would be great if you could send
all 5 to @FlickType.

George, sounds like both you and Chuck had some issue while trying to
manually type the letter A. Could you please also check to see if you
have any FlickType crash logs from the last couple of days?

Below are steps to share a crash report from your iPhone:
1. Go to the iOS Settings app.
2. Go to Privacy.
3. Go to Analytics or Diagnostics & Usage.
4. Select Analytics Data or Diagnostics & Usage Data.

Thank you,
Kosta





Re: Build 115 problems

 

Thank you Chuck, I got them and I'm investigating. FYI you sent them
to the group email rather than the @FlickType, but they were
pending moderation.

Kosta

On Thu, Jun 28, 2018 at 9:52 PM Chuck Dean <cadean329@...> wrote:

Hi,
My mistake, there were only four crash reports for today. I sent them.
Chuck

On Jun 28, 2018, at 9:45 PM, FlickType <@FlickType> wrote:

Thank you Chuck. Once you open a crash report, there is a share button
at the top right of the screen. It would be great if you could send
all 5 to @FlickType.

George, sounds like both you and Chuck had some issue while trying to
manually type the letter A. Could you please also check to see if you
have any FlickType crash logs from the last couple of days?

Below are steps to share a crash report from your iPhone:
1. Go to the iOS Settings app.
2. Go to Privacy.
3. Go to Analytics or Diagnostics & Usage.
4. Select Analytics Data or Diagnostics & Usage Data.

Thank you,
Kosta




Re: Build 115 problems

Chuck Dean
 

Hi,
My mistake, there were only four crash reports for today. I sent them.
Chuck

On Jun 28, 2018, at 9:45 PM, FlickType <@FlickType> wrote:

Thank you Chuck. Once you open a crash report, there is a share button
at the top right of the screen. It would be great if you could send
all 5 to @FlickType.

George, sounds like both you and Chuck had some issue while trying to
manually type the letter A. Could you please also check to see if you
have any FlickType crash logs from the last couple of days?

Below are steps to share a crash report from your iPhone:
1. Go to the iOS Settings app.
2. Go to Privacy.
3. Go to Analytics or Diagnostics & Usage.
4. Select Analytics Data or Diagnostics & Usage Data.

Thank you,
Kosta



Re: Build 115 problems

 

Thank you Chuck. Once you open a crash report, there is a share button
at the top right of the screen. It would be great if you could send
all 5 to @FlickType.

George, sounds like both you and Chuck had some issue while trying to
manually type the letter A. Could you please also check to see if you
have any FlickType crash logs from the last couple of days?

Below are steps to share a crash report from your iPhone:
1. Go to the iOS Settings app.
2. Go to Privacy.
3. Go to Analytics or Diagnostics & Usage.
4. Select Analytics Data or Diagnostics & Usage Data.

Thank you,
Kosta


Re: Build 115 problems

George Cham
 

Just had a red screen issue while typing with build 115.
I typed the word table. Then did a long hold for a.. That's when the red screen came up.

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: Friday, June 29, 2018 2:06:28 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 115 problems
 
Thank you Chuck. That sounds like a crash. Could you please check for any crash reports on your device?

Below are steps to share a crash report from your iPhone.

  1. Go to the iOS Settings app.
  2. Go to Privacy.
  3. Go to Analytics or Diagnostics & Usage.
  4. Select Analytics Data or Diagnostics & Usage Data.
The flicktype logs should now all begin with the word flicktype. 

Thanks,
Kosta 

On Jun 28, 2018, at 20:59, Chuck Dean <cadean329@...> wrote:


I was trying to reply to an email. When I flicked right to insert the period and the screen flashed and it changed to the iOS keyboard.
As I entered that last period the screen went red.

8:58 PDT.
Chuck

On Jun 28, 2018, at 8:41 PM, Chuck Dean <cadean329@...> wrote:

Hello Kosta,
Right now I am getting a lot of red screens.
Typing in my journal I lost a couple of words after I typed motto A. When I flicked to insert the period the screen flashed and I lost some words. It sounds weird but it seems to have something to do with the capital A.
Also, when I dismissed the keyboard, and then went back to add text the first line of text in the entry is repeated as the last line.
Chuck
By the way, this happened approximately 830 Pacific daylight Time






Re: Build 115 problems

Chuck Dean
 

Hi,
I have five crash reports in the analytics. The latest one was about the time that the app crashed. What do you want me to send you from the report. It is 25 pages long.
Chuck

On Jun 28, 2018, at 9:06 PM, FlickType <hello@...> wrote:

Thank you Chuck. That sounds like a crash. Could you please check for any crash reports on your device?

Below are steps to share a crash report from your iPhone.

  1. Go to the iOS Settings app.
  2. Go to Privacy.
  3. Go to Analytics or Diagnostics & Usage.
  4. Select Analytics Data or Diagnostics & Usage Data.
The flicktype logs should now all begin with the word flicktype. 

Thanks,
Kosta 

On Jun 28, 2018, at 20:59, Chuck Dean <cadean329@...> wrote:


I was trying to reply to an email. When I flicked right to insert the period and the screen flashed and it changed to the iOS keyboard.
As I entered that last period the screen went red.

8:58 PDT.
Chuck

On Jun 28, 2018, at 8:41 PM, Chuck Dean <cadean329@...> wrote:

Hello Kosta,
Right now I am getting a lot of red screens.
Typing in my journal I lost a couple of words after I typed motto A. When I flicked to insert the period the screen flashed and I lost some words. It sounds weird but it seems to have something to do with the capital A.
Also, when I dismissed the keyboard, and then went back to add text the first line of text in the entry is repeated as the last line.
Chuck
By the way, this happened approximately 830 Pacific daylight Time






Re: Build 115 problems

 

Thank you Chuck. That sounds like a crash. Could you please check for any crash reports on your device?

Below are steps to share a crash report from your iPhone.

  1. Go to the iOS Settings app.
  2. Go to Privacy.
  3. Go to Analytics or Diagnostics & Usage.
  4. Select Analytics Data or Diagnostics & Usage Data.
The flicktype logs should now all begin with the word flicktype. 

Thanks,
Kosta 

On Jun 28, 2018, at 20:59, Chuck Dean <cadean329@...> wrote:


I was trying to reply to an email. When I flicked right to insert the period and the screen flashed and it changed to the iOS keyboard.
As I entered that last period the screen went red.

8:58 PDT.
Chuck

On Jun 28, 2018, at 8:41 PM, Chuck Dean <cadean329@...> wrote:

Hello Kosta,
Right now I am getting a lot of red screens.
Typing in my journal I lost a couple of words after I typed motto A. When I flicked to insert the period the screen flashed and I lost some words. It sounds weird but it seems to have something to do with the capital A.
Also, when I dismissed the keyboard, and then went back to add text the first line of text in the entry is repeated as the last line.
Chuck
By the way, this happened approximately 830 Pacific daylight Time






Re: Build 114 prediction not as good?

Ed Worrell
 

I to am having more mistakes than I used to with the predictive engine. I have noticed that if I make over exaggerated gestures whilst typing it seems to be more accurate. Just my findings so far.

I have not had any issues with memory loss or text loss.

Ed

On Jun 28, 2018, at 9:42 PM, Salman Haider <salmanhaider.purdue@...> wrote:

I have definitely noticed this as well.
Infact, I have to say that I have noticed a regression in the app's
ability to predict correctly at various points during the development
cycle/process. In certain releases, the app's prediction engine works
very well. Others, not so much.
It's a random thing. However, in the few times that I have mentioned
it on the list, it hasn't seemed like others have encountered the
issue as much or as frequently.
I have not said anything about it ever since, thinking maybe it's just me.
I also have to say that I never started a brand new discussion thread
about it, each time I experienced this issue with a certain release.

That said, version 114 has definitely given me more issues with
getting the accurate prediction, just like various other random
releases have in the past. This time too, I did not mention it right
away, thinking that like before, maybe it's just me who has felt it.
So in a way, I am glad that more people are experiencing the same
issue as well and reporting it.
I think it would allow Kosta to tackle the problem more effectively
and efficiently, the more reports he receives.
Obviously the prediction engine becoming a bit more inaccurate is an
issue being caused inadvertently.

Version 112 seems to work quite well for me and that's what I have on
my device at this time.

On 6/28/18, Chuck Dean <cadean329@...> wrote:
Build 114 prediction not as good?
Hello everyone,
Is it my imagination or is the predictions in build 114 a little off? It
seems like I am having to swipe down a lot more than usual.
For example I went to type the word "on" end the first prediction was "of".


Anyone else having this problem?

Chuck





Re: Build 115 problems

Chuck Dean
 

I was trying to reply to an email. When I flicked right to insert the period and the screen flashed and it changed to the iOS keyboard.
As I entered that last period the screen went red.

8:58 PDT.
Chuck

On Jun 28, 2018, at 8:41 PM, Chuck Dean <cadean329@...> wrote:

Hello Kosta,
Right now I am getting a lot of red screens.
Typing in my journal I lost a couple of words after I typed motto A. When I flicked to insert the period the screen flashed and I lost some words. It sounds weird but it seems to have something to do with the capital A.
Also, when I dismissed the keyboard, and then went back to add text the first line of text in the entry is repeated as the last line.
Chuck
By the way, this happened approximately 830 Pacific daylight Time


Re: Build 114 prediction not as good?

Salman Haider
 

I have definitely noticed this as well.
Infact, I have to say that I have noticed a regression in the app's
ability to predict correctly at various points during the development
cycle/process. In certain releases, the app's prediction engine works
very well. Others, not so much.
It's a random thing. However, in the few times that I have mentioned
it on the list, it hasn't seemed like others have encountered the
issue as much or as frequently.
I have not said anything about it ever since, thinking maybe it's just me.
I also have to say that I never started a brand new discussion thread
about it, each time I experienced this issue with a certain release.

That said, version 114 has definitely given me more issues with
getting the accurate prediction, just like various other random
releases have in the past. This time too, I did not mention it right
away, thinking that like before, maybe it's just me who has felt it.
So in a way, I am glad that more people are experiencing the same
issue as well and reporting it.
I think it would allow Kosta to tackle the problem more effectively
and efficiently, the more reports he receives.
Obviously the prediction engine becoming a bit more inaccurate is an
issue being caused inadvertently.

Version 112 seems to work quite well for me and that's what I have on
my device at this time.

On 6/28/18, Chuck Dean <cadean329@...> wrote:
Build 114 prediction not as good?
Hello everyone,
Is it my imagination or is the predictions in build 114 a little off? It
seems like I am having to swipe down a lot more than usual.
For example I went to type the word "on" end the first prediction was "of".


Anyone else having this problem?

Chuck




Build 115 problems

Chuck Dean
 

Hello Kosta,
Right now I am getting a lot of red screens.
Typing in my journal I lost a couple of words after I typed motto A. When I flicked to insert the period the screen flashed and I lost some words. It sounds weird but it seems to have something to do with the capital A.
Also, when I dismissed the keyboard, and then went back to add text the first line of text in the entry is repeated as the last line.
Chuck
By the way, this happened approximately 830 Pacific daylight Time


Build 115

 

- Added "User ID" field at the bottom of Settings screen to help resolve reports of subscription-releated issues.
- Changed error messages of the custom keyboard when full access is not enabled or the subscription is inactive.
- Added startup alert to inform users that VoiceOver is required.
- Fixed a rare casing error.

Please report any text loss issues, or if you are experiencing any change in accuracy. If the accuracy seems to be similar to most previous builds, please let us know as well. We have not aimed to change the accuracy in any way in any of the recent builds.

Thank you,
Kosta


Re: A fund for those who can not afford FlickType?

Ed Worrell
 

Hey chuck,

I am with you. I have wondered that at times too...

I believe that you can gift an app, but that's only if there is a purchase price. I don't think you can do it with subscriptions. I don't think there's a way unless you send them a gift card for the yearly price.

I hope this helps,

Ed

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


Hello everyone,
Although I find it hard to believe that someone who owns an iPhone couldn't afford to subscribe to FlickType, I was thinking of funding a project to aid those less fortunate.. Does anyone have any ideas how to verify someone is actually in need and not just trying to get a free ride?
Also, is it possible for me to pay for someone subscription?
Just spitballing.
Chuck