Date   
Re: Learning more about you #poll

George Cham
 

Hi Ashley and Coster,
I would like to see unlimited emojis, A half screen keyboard, and the ability to switch between half screen and  fullscreen. Also I would like the option of having the     numbers row   Always showing  at the top of the keyboard. instead of Magic capping in order to switch between numbers and letters

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, July 24, 2018 6:11:13 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Learning more about you
 
Hi Alpha Group,

Would you please send us your wish list for what you'd like for us to work on next? We're going to be sending the poll as well as asking what the larger group would like for us to work on next and we'd appreciate your suggestions before sending it out.

Thanks!
Ashley



Bild 144

 

- Keys will now be shown by default. Can be turned off in the settings.
- Visual tweaks to keyboard area when keys are hidden.
- Visual announcements will now take up more than one line if needed, rather than squeeze the announcement text all in one line by making the font extremely small.
- When reading back the typed text, it will now also be shown as a multiline visual announcement.
- "System" announcements such as switching to numbers or invoking shift will now appear yellow and have a slightly higher pitch.
- Added a workaround setting for the WhatsApp crash, off by default. Enable "Reduced Height" in the settings only if you have been experiencing crashes with WhatsApp.
- Removed confusing "Inactive" badge on Upgrade tab item.
- Added hint on how to change the preset emoji setting.

Re: Learning more about you #poll

 

Hi Alpha Group,

Would you please send us your wish list for what you'd like for us to work on next? We're going to be sending the poll as well as asking what the larger group would like for us to work on next and we'd appreciate your suggestions before sending it out.

Thanks!
Ashley

Learning more about you #poll

 

As we’re preparing to move on to the next steps with FlickType we’d like to learn a little more about you to better help us build the best product possible. What level of sight do you have?

Thank you for voting.


Re: Email list...

 

Hi Guys,

Thanks for checking in, we're still here working away! You haven't heard much from us because we were working on the WhatsApp issue, which was uneventful and now we've moved on to some user interface work, which is slow moving. We're wrapping up the interface work today, so we'll be sending out a poll in a few to get some input on what we should focus on next.

Warmly,
Ashley

Re: Email list...

Paul Sutton
 

Same here, its been quite quiet for a while.

On 20 Jul 2018, at 15:39, Ed Worrell via Groups.Io <ed.worrell=icloud.com@groups.io> wrote:



Hello all,

I was just wondering if there had been any further development on FlickType? The list has been really quiet as of late... ☺️

Thanks and I hope everything is well. Ed Worrell

Re: Email list...

Benny Barber
 

Yeah, I miss the updates. I'm getting a little bored.
Benny

On Jul 20, 2018, at 9:39 AM, Ed Worrell via Groups.Io <ed.worrell=icloud.com@groups.io> wrote:



Hello all,

I was just wondering if there had been any further development on FlickType? The list has been really quiet as of late... ☺️

Thanks and I hope everything is well. Ed Worrell

Email list...

Ed Worrell
 

Hello all,

I was just wondering if there had been any further development on FlickType? The list has been really quiet as of late... ☺️

Thanks and I hope everything is well. Ed Worrell

Re: A little problem

David Nason
 

Hi Michael,

I have not come across this issue.
The only thing I can think of is that perhaps you are accidentally envoking the swipe up and hold and / or the swipe down and hold gestures, which dismiss the keyboard.

Dave

On 17 Jul 2018, at 08:53, Michael Maslo <michaelmaslo04@...> wrote:

Hello list,

Not sure if anyone else is having this issue or not. I will start typing a email or a text and my keyboard will go away. I have to double click in the edit box to get it back. This only happens after I have typed a word and then flick up or down. This is not a all the time issue and it can not be duplicated on any type of regular basis..

Any ideas would be appreciated.


A little problem

Michael Maslo
 

Hello list,

Not sure if anyone else is having this issue or not. I will start typing a email or a text and my keyboard will go away. I have to double click in the edit box to get it back. This only happens after I have typed a word and then flick up or down. This is not a all the time issue and it can not be duplicated on any type of regular basis..

Any ideas would be appreciated.

Re: Whatsapp crashing. Re: [FlickType-alpha] Build 131

Macster
 

Hi Kosta, 

Apologies for slow reply, just back from holiday. I've been experiencing the what's app crash too over the last couple of days too. I've been trying to narrow down the cause but so far it's inconsistent, though it does seem to be exclusive to my two large group threads which are by some distance the largest conversations I have. I've tried deleting FlickType from my keyboard list. And going back in to type with the iOS keyboard. This appears to bypass the crash, then I added FlickType back and one thread no longer crashed and one did, even after repeating this process with a restart of my phone in between. A difficult one to pinpoint. 

Macky 


On 13 Jul 2018, at 02:58, FlickType <hello@...> wrote:

Thank you George. Just so everyone's aware, I've send build 138 only to Salman and David to assist with the WhatsApp crash. If anyone else has experienced the WhatsApp crash, let me know and I can send you a special investigative version as well.

As I understand it, the crash happens only sometimes, and seems to be happening right as soon as you double tap to edit a conversation textfield. Please correct me if I'm wrong.

It's also been mentioned that the crash may be more likely in some threads but not others, although I don't know how confident we can be there's a pattern there, because I simply don't know how many times the crash has occurred in comparison which how many times it didn't and things just worked as expected. If anyone can reliably reproduce it with a particular thread, and reliably NOT reproduce it with another thread, say 6 times in a row, then that could indicate a pattern with the threads.

Finally, FlickType does not seem to be the one crashing here, so it's more difficult than usual to figure out what's going on. In case it helps anyone to figure a pattern, the WhatsApp crash log indicates that at the time of the crash, WhatsApp was repeatedly trying to change the contents or layout of its view. I'm just sharing this because it's all I got, smile.

- Kosta

Re: Version 138 WhatsApp crash reports

 

I still haven't been able to reproduce the issue. But based on Salman's reports, one theory I have is that whatever is the root cause, once the issue occurs it is way more likely to occur again in the same thread. I have sent build 139 to Salman and David, as well as a couple folks from the beta group. This build has a speculative fix to prevent at least some of the repeat crashes. Please let me know if this feels any different, better or worse.

Thank you for testing!
- Kosta

Re: Version 138 WhatsApp crash reports

Salman Haider
 

One more update. Just went in and attempted to type a message, it
worked once. I was able to successfully type and send the message;
10:37pm.
Exited the app, went back in, switched to Flicktype to type again. App
crashed. This happened at 10:39pm.
Went back again, app crashed immediately. Also at 10:39pm.

Received a message, went back to read and reply. Was able to type and
send a message at 10:42pm. Returned to thread to attempt typing again,
app crashed at 10:43pm.

On 7/12/18, Salman Haider <salmanhaider.purdue@...> wrote:
Kosta,

Another crash, 10:09pm EST. Same thread.
It is now happening quite consistently for me.
The only way I am able to go back and enter text in that field under
that particular thread again is, to navigate to a different thread,
double tap the field there to bring up the keyboard. The Flicktype
keyboard comes up (this is interesting to me, which I describe in the
next paragraph). I flick up and hold to revert back to the iOS
keyboard, then exit out of that thread, return to the initial thread,
double tap the text field, and the iOS keyboard comes up. No crash.
As soon as I switch keyboards to Flicktype again, the app crashes.

Now, I do want to bring your attention to one thing though. Lets call
the thread that's causing the crashes, Thread A. And lets refer to the
other random thread, the one I go to to revert back to the iOS
keyboard, Thread B.

When I go to Thread B and double tap the field, as I mentioned before,
it's the Flicktype keyboard that comes up by default, and not the iOS
keyboard. This, I find odd because the iOS keyboard should be the one
coming up, rather than Flicktype, considering the fact that I always
revert back to the iOS keyboard in any window that I'm typing in.

So, it's like, it's somehow stuck on the Flicktype keyboard ever since
my attempt to type using that keyboard in Thread A.
And it needs to be reverted back to the iOS keyboard in Thread B. But
when I go back into Thread A again and switch keyboards to Flicktype,
Whatsapp crashes.
If I immediately go back into Whatsapp and try typing in Thread A
again, Whatsapp crashes right away after attempting to load the
keyboard.
This is one way that I've been able to reproduce the issue relatively
consistently.

I don't have enough vision to tell you what keyboard, if any, is shown
for that split second prior to the crash, but I am relatively
confident that it's the Flicktype keyboard that is being loaded at
that moment. Since the entire screen goes dark for a second like it
does when I have the Flicktype keyboard up.
Plus, navigating back to Thread B confirms that it's somehow stuck on
Flicktype rather than the iOS keyboard.

I hope this makes some sort of sense. It's a bit tricky to explain, so
I've tried to explain it in the best way possible. Let me know if this
helps or if you require any clarification on anything.

Salman

On 7/12/18, Salman Haider <salmanhaider.purdue@...> wrote:
Happening much more consistently now. Three back to back crashes at
9:53pm
EST.


On 7/12/18, Salman Haider <salmanhaider.purdue@...> wrote:
Reporting three more crashes. 9:47pm EST, 9:49pm EST, 9:50pm EST.
Salman

On 7/12/18, Salman Haider <salmanhaider.purdue@...> wrote:
However, I am not being able to reproduce the issue consistently. It
was
happening 100% of the time prior to installing this new update, now
though,
it has happened only once, and I have tried to go into the thread five,
maybe six times. I will keep checking.

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

Hi Kosta, after installing the latest update, I went to the same
thread.
Initially there was no crash. However, no messages were exchanged.
I went into the thread again just a few minutes ago and Whatsapp
crashed.
The time was 9:21pm EST.
Salman










Re: Version 138 WhatsApp crash reports

 

Thank you Salman, this is very helpful. I'm gonna try to reproduce based on this.

- Kosta

Re: Version 138 WhatsApp crash reports

Salman Haider
 

Kosta,

Another crash, 10:09pm EST. Same thread.
It is now happening quite consistently for me.
The only way I am able to go back and enter text in that field under
that particular thread again is, to navigate to a different thread,
double tap the field there to bring up the keyboard. The Flicktype
keyboard comes up (this is interesting to me, which I describe in the
next paragraph). I flick up and hold to revert back to the iOS
keyboard, then exit out of that thread, return to the initial thread,
double tap the text field, and the iOS keyboard comes up. No crash.
As soon as I switch keyboards to Flicktype again, the app crashes.

Now, I do want to bring your attention to one thing though. Lets call
the thread that's causing the crashes, Thread A. And lets refer to the
other random thread, the one I go to to revert back to the iOS
keyboard, Thread B.

When I go to Thread B and double tap the field, as I mentioned before,
it's the Flicktype keyboard that comes up by default, and not the iOS
keyboard. This, I find odd because the iOS keyboard should be the one
coming up, rather than Flicktype, considering the fact that I always
revert back to the iOS keyboard in any window that I'm typing in.

So, it's like, it's somehow stuck on the Flicktype keyboard ever since
my attempt to type using that keyboard in Thread A.
And it needs to be reverted back to the iOS keyboard in Thread B. But
when I go back into Thread A again and switch keyboards to Flicktype,
Whatsapp crashes.
If I immediately go back into Whatsapp and try typing in Thread A
again, Whatsapp crashes right away after attempting to load the
keyboard.
This is one way that I've been able to reproduce the issue relatively
consistently.

I don't have enough vision to tell you what keyboard, if any, is shown
for that split second prior to the crash, but I am relatively
confident that it's the Flicktype keyboard that is being loaded at
that moment. Since the entire screen goes dark for a second like it
does when I have the Flicktype keyboard up.
Plus, navigating back to Thread B confirms that it's somehow stuck on
Flicktype rather than the iOS keyboard.

I hope this makes some sort of sense. It's a bit tricky to explain, so
I've tried to explain it in the best way possible. Let me know if this
helps or if you require any clarification on anything.

Salman

On 7/12/18, Salman Haider <salmanhaider.purdue@...> wrote:
Happening much more consistently now. Three back to back crashes at 9:53pm
EST.


On 7/12/18, Salman Haider <salmanhaider.purdue@...> wrote:
Reporting three more crashes. 9:47pm EST, 9:49pm EST, 9:50pm EST.
Salman

On 7/12/18, Salman Haider <salmanhaider.purdue@...> wrote:
However, I am not being able to reproduce the issue consistently. It was
happening 100% of the time prior to installing this new update, now
though,
it has happened only once, and I have tried to go into the thread five,
maybe six times. I will keep checking.

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

Hi Kosta, after installing the latest update, I went to the same thread.
Initially there was no crash. However, no messages were exchanged.
I went into the thread again just a few minutes ago and Whatsapp
crashed.
The time was 9:21pm EST.
Salman










Re: Whatsapp crashing. Re: [FlickType-alpha] Build 131

Salman Haider
 

Hi Kosta,
You are correct. The crash happens when I double tap in the text field
to bring up the keyboard.
I have noticed something else, which I'll describe under the crash
reports thread.
Salman

On 7/12/18, FlickType <@FlickType> wrote:
Thank you George. Just so everyone's aware, I've send build 138 only to
Salman and David to assist with the WhatsApp crash. If anyone else has
experienced the WhatsApp crash, let me know and I can send you a special
investigative version as well.

As I understand it, the crash happens only sometimes, and seems to be
happening right as soon as you double tap to edit a conversation textfield.
Please correct me if I'm wrong.

It's also been mentioned that the crash may be more likely in some threads
but not others, although I don't know how confident we can be there's a
pattern there, because I simply don't know how many times the crash has
occurred in comparison which how many times it didn't and things just
worked as expected. If anyone can reliably reproduce it with a particular
thread, and reliably NOT reproduce it with another thread, say 6 times in a
row, then that could indicate a pattern with the threads.

Finally, FlickType does not seem to be the one crashing here, so it's more
difficult than usual to figure out what's going on. In case it helps anyone
to figure a pattern, the WhatsApp crash log indicates that at the time of
the crash, WhatsApp was repeatedly trying to change the contents or layout
of its view. I'm just sharing this because it's all I got, smile.

- Kosta



Re: Whatsapp crashing. Re: [FlickType-alpha] Build 131

 

Thank you George. Just so everyone's aware, I've send build 138 only to Salman and David to assist with the WhatsApp crash. If anyone else has experienced the WhatsApp crash, let me know and I can send you a special investigative version as well.

As I understand it, the crash happens only sometimes, and seems to be happening right as soon as you double tap to edit a conversation textfield. Please correct me if I'm wrong.

It's also been mentioned that the crash may be more likely in some threads but not others, although I don't know how confident we can be there's a pattern there, because I simply don't know how many times the crash has occurred in comparison which how many times it didn't and things just worked as expected. If anyone can reliably reproduce it with a particular thread, and reliably NOT reproduce it with another thread, say 6 times in a row, then that could indicate a pattern with the threads.

Finally, FlickType does not seem to be the one crashing here, so it's more difficult than usual to figure out what's going on. In case it helps anyone to figure a pattern, the WhatsApp crash log indicates that at the time of the crash, WhatsApp was repeatedly trying to change the contents or layout of its view. I'm just sharing this because it's all I got, smile.

- Kosta

Re: Version 138 WhatsApp crash reports

Salman Haider
 

Happening much more consistently now. Three back to back crashes at 9:53pm EST.

On 7/12/18, Salman Haider <salmanhaider.purdue@...> wrote:
Reporting three more crashes. 9:47pm EST, 9:49pm EST, 9:50pm EST.
Salman

On 7/12/18, Salman Haider <salmanhaider.purdue@...> wrote:
However, I am not being able to reproduce the issue consistently. It was
happening 100% of the time prior to installing this new update, now
though,
it has happened only once, and I have tried to go into the thread five,
maybe six times. I will keep checking.

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

Hi Kosta, after installing the latest update, I went to the same thread.
Initially there was no crash. However, no messages were exchanged.
I went into the thread again just a few minutes ago and Whatsapp crashed.
The time was 9:21pm EST.
Salman








Re: Version 138 WhatsApp crash reports

Salman Haider
 

Reporting three more crashes. 9:47pm EST, 9:49pm EST, 9:50pm EST.
Salman

On 7/12/18, Salman Haider <salmanhaider.purdue@...> wrote:
However, I am not being able to reproduce the issue consistently. It was
happening 100% of the time prior to installing this new update, now though,
it has happened only once, and I have tried to go into the thread five,
maybe six times. I will keep checking.

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

Hi Kosta, after installing the latest update, I went to the same thread.
Initially there was no crash. However, no messages were exchanged.
I went into the thread again just a few minutes ago and Whatsapp crashed.
The time was 9:21pm EST.
Salman






Re: Whatsapp crashing. Re: [FlickType-alpha] Build 131

George Cham
 

Hi costa, not getting error message with whats app with build 137. But getting red screen

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: 32441125320n behalf of
Sent: Friday, July 13, 2018 11:36 am
To: alpha@flicktype.groups.io
Subject: Re: Whatsapp crashing. Re: [FlickType-alpha] Build 131
 
Yes, they don't seem to be aware of any issues between Whatsapp and third party keyboards. I am also wondering if this issue is VoiceOver specific? As in, a third party keyboard being used in Whatsapp, with VoiceOver enabled?
Just a thought.
Salman

On Jul 12, 2018, at 6:30 PM, David Nason <dnason@...> wrote:


I've reported the issue to WhatsApp as well, they say they are looking at the log files and will investigate, but it seems it is not currently a known issue to them.
Can you also report it to them Salman?

It probably will affect other message threads I'm afraid. However it may also stop affecting the one that is currently crashing.

Dave
> On 12 Jul 2018, at 23:16, Salman Haider <salmanhaider.purdue@...> wrote:
>
> And agreed. Could very well be an issue with Whatsapp and third party keyboards and nothing to do with Flicktype. So far though, thankfully it hasn't happened on any other thread. Hope it stays that way. Fingers crossed.
>
> On Jul 12, 2018, at 6:07 PM, Salman Haider <salmanhaider.purdue@...> wrote:
>
> So far it’s only happening on one thread for me, but it may change. I hope not, otherwise, I will pretty much have to revert to the Flicktype classic app since WhatsApp is probably the app that I use most often with Flicktype. That, and FB Messenger. Very strange behavior. And quite frustrating
>
> On Jul 12, 2018, at 5:49 PM, David Nason <dnason@...> wrote:
>
>
> Hi Salman and Kosta,
>
> This issue has continued to occur to me too in recent days.
> Sometimes it will crash once and then be ok, but other times a specific message thread will just continue to crash no matter how many times I try it.
> It's not always the same message thread either, it's currently affecting a different one to the one being affected most often when I first reported it.
>
> Of course it could be the case that WhatsApp has a bug with third party keyboards, as opposed to an issue with FlickType. Might be worth contacting them too.
>
> Dave
>> On 12 Jul 2018, at 22:29, FlickType <hello@...> wrote:
>>
>> Salman, could you please send us a couple of the latest crash reports for WhatsApp that may be on your device? You can find those under iOS Settings, Privacy, Analytics, Analytics Data.
>>
>> Thanks,
>> Kosta
>>
>>
>>
>
>
>
>
>
>
>
>
>