Date   

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

Salman Haider
 

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 <@FlickType> 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










Re: Version 138 WhatsApp crash reports

Salman Haider
 

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


Version 138 WhatsApp crash reports

Salman Haider
 

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

 

Thank you all. From the logs, I can see that WhatsApp is going into a never-ending loop of some sorts and then crashes. The tricky part is that there is no indication about what FlickType is doing at the time, and there is also no indication that FlickType itself ever crashes so that we'd get some logs.

Can either of you, or anyone else, currently reliably reproduce the issue? If so, I could try to create a special FlickType build with some more logs turned on and send it only to you in order to help debug the issue.

- Kosta


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

David Nason
 

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 <@FlickType> 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










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

Salman Haider
 

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 <@FlickType> 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



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

Salman Haider
 

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 <@FlickType> 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



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

Salman Haider
 

Just sent the two latest ones to @FlickType

On Jul 12, 2018, at 5:29 PM, FlickType <@FlickType> 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


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

David Nason
 

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 <@FlickType> 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



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

 

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


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

Salman Haider
 

Not at all. Plain old text. Not even any numbers or emoji or symbols.In fact, we usually exchange voice messages but in this case, those haven't been exchanged in recent days either.
 

On Jul 12, 2018, at 5:20 PM, FlickType <hello@...> wrote:

Thank you Salman.

We are currently investigating this. Is there anything unusual that you or your friend typed into the thread just before you started experiencing the issue?

- Kosta


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

 

Thank you Salman.

We are currently investigating this. Is there anything unusual that you or your friend typed into the thread just before you started experiencing the issue?

- Kosta


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

Salman Haider
 

Hi Kosta,
I have begun encountering the exact same issue, just out of the blue. It is exactly how Dave describes it here, word for word. Everything is exactly the same.
The only difference is, I am on iOS 11.4.1.
Also, I am on version 137 of Flicktype. However, like dave says, the issue isn't version specific. Its happening while FlickType itself is installed. When I uninstall it, the issue disappears.

Dave, were you able to find a way to get around this issue? I have tried everything that you have stated here, apart from deleting the thread itself. Which is definitely not something I can afford to do here.
Any help would be appreciated.

Salman

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

Hi Kosta,

This build is crashing WhatsApp for me.
Its a strange one though. When I open particular message threads, and double tap on the text field in order to type, the app crashes. Other message threads will be just fine.

Its definitely FlickType causing the issue because when I delete it, the crashes stop, and when I install it again, the crashes occur again.


In fact previous builds seem to be doing it too.
I am running iOS 12 beta, which yesterday updated to beta 3, so perhaps that’s related.

Dave
On 4 Jul 2018, at 07:46, FlickType <@FlickType> wrote:

- Internal changes



First line of text replacement, bug

Rocco Fiorentino
 

Hi All,

I think I just was able to reproduce a bug that someone was talking about a few days ago, maybe Chuck? I wrote a text in Messages with the FlickType keyboard, then dismissed the keyboard, and realized that a word in the beginning of the message was wrong. I went back into FlickType to try and edit, but it only saw the last 3 words in the text, "call me later." I then exited Flicktype again, and went to the top of the message by double tapping the text field twice, thinking this would somehow refresh Flicktype’s recognition of what was already present in the text field. However, Flicktype instead replaced the first few words of the text, the one’s I was trying to fix in the first place, with "call me later."

Not sure if this makes sense, or how else to describe this, but just wanted to let you know. I’ll try and reproduce it again to be sure.

Thanks so much,

Rocco


Re: Build 137

 

Thank you Chanelle, I’ll take a look.

Kosta

On Jul 11, 2018, at 11:21, Chanelle Allen <chanellem.allen@...> wrote:


Hi Kosta
In my testing, there are no spaces between quotation marks and punctuation marks or letters, and there is a space between the end of a sentence and an emoji. Those issues have been fixed. However, I discovered a peculiar bug when typing a quotation mark at the beginning of a sentence. Here's a sample sentence. "hello, how are you?"
You will notice that the word hello in that sentence was not capitalized even though it was the first word. When writing the quotation mark, I use a two finger double tap to toggle numbers. After typing the quote, I perform another two finger double tap to switch to letters. FlickType announces "Letters lowercase." a two finger single tap toggles to uppercase. I type the word at the beginning of my sentence. But ... FlickType spells out each suggestion with the first letter in lowercase. To work around the problem, I flick left to delete, turn on uppercase, and then finally hear my desired word with a capital letter. I cannot find any FlickType logs with today's date. I was practicing with the Drafts app, but the example has been reproduced in Mail as well. I have an iPhone 7 running iOS 11.4.1, released Monday.
Thank you.
Chanelle

On Jul 11, 2018, at 01:44, David Nason <dnason@...> wrote:


Hi Kosta,

I too can confirm that the quotation marks are now working correctly, with no crashes.

Dave
On 11 Jul 2018, at 01:00, Benny Barber <rebelben@...> wrote:


In my testing of the quote and emoji spacing, everything worked just fine. Good work, Kosta. Thanks
Benny

On Jul 10, 2018, at 6:27 PM, FlickType <@FlickType> wrote:

Please test the new quote and emoji spacing functionality and report any unexpected behavior, ideally with a small reproducible example.

What's new:
- Crash fix

Previously:
- A space will now be inserted before the first typed emoji. No spaces will be inserted between consecutive emojis.
- Unwanted spaces around quotes will now be stripped.
- FlickType hint announcements have been limited to the first 3 times since launching the keyboard. This will reset whenever the keyboard is relaunched, which happens if you reboot your device, if you update FlickType, if FlickType crashed, or if full access is toggled in the settings. So while this won't prevent the hints entirely for those who really don't need them, it will silence them for the vast majority of the cases.

Thank you for testing FlickType!

Warmly,
Kosta and Ashley







Re: Build 137

Chanelle Allen
 

Hi Kosta
In my testing, there are no spaces between quotation marks and punctuation marks or letters, and there is a space between the end of a sentence and an emoji. Those issues have been fixed. However, I discovered a peculiar bug when typing a quotation mark at the beginning of a sentence. Here's a sample sentence. "hello, how are you?"
You will notice that the word hello in that sentence was not capitalized even though it was the first word. When writing the quotation mark, I use a two finger double tap to toggle numbers. After typing the quote, I perform another two finger double tap to switch to letters. FlickType announces "Letters lowercase." a two finger single tap toggles to uppercase. I type the word at the beginning of my sentence. But ... FlickType spells out each suggestion with the first letter in lowercase. To work around the problem, I flick left to delete, turn on uppercase, and then finally hear my desired word with a capital letter. I cannot find any FlickType logs with today's date. I was practicing with the Drafts app, but the example has been reproduced in Mail as well. I have an iPhone 7 running iOS 11.4.1, released Monday.
Thank you.
Chanelle

On Jul 11, 2018, at 01:44, David Nason <dnason@...> wrote:


Hi Kosta,

I too can confirm that the quotation marks are now working correctly, with no crashes.

Dave
On 11 Jul 2018, at 01:00, Benny Barber <rebelben@...> wrote:


In my testing of the quote and emoji spacing, everything worked just fine. Good work, Kosta. Thanks
Benny

On Jul 10, 2018, at 6:27 PM, FlickType <@FlickType> wrote:

Please test the new quote and emoji spacing functionality and report any unexpected behavior, ideally with a small reproducible example.

What's new:
- Crash fix

Previously:
- A space will now be inserted before the first typed emoji. No spaces will be inserted between consecutive emojis.
- Unwanted spaces around quotes will now be stripped.
- FlickType hint announcements have been limited to the first 3 times since launching the keyboard. This will reset whenever the keyboard is relaunched, which happens if you reboot your device, if you update FlickType, if FlickType crashed, or if full access is toggled in the settings. So while this won't prevent the hints entirely for those who really don't need them, it will silence them for the vast majority of the cases.

Thank you for testing FlickType!

Warmly,
Kosta and Ashley






Re: Build 137

David Nason
 

Hi Kosta,

I too can confirm that the quotation marks are now working correctly, with no crashes.

Dave

On 11 Jul 2018, at 01:00, Benny Barber <rebelben@...> wrote:


In my testing of the quote and emoji spacing, everything worked just fine. Good work, Kosta. Thanks
Benny

On Jul 10, 2018, at 6:27 PM, FlickType <@FlickType> wrote:

Please test the new quote and emoji spacing functionality and report any unexpected behavior, ideally with a small reproducible example.

What's new:
- Crash fix

Previously:
- A space will now be inserted before the first typed emoji. No spaces will be inserted between consecutive emojis.
- Unwanted spaces around quotes will now be stripped.
- FlickType hint announcements have been limited to the first 3 times since launching the keyboard. This will reset whenever the keyboard is relaunched, which happens if you reboot your device, if you update FlickType, if FlickType crashed, or if full access is toggled in the settings. So while this won't prevent the hints entirely for those who really don't need them, it will silence them for the vast majority of the cases.

Thank you for testing FlickType!

Warmly,
Kosta and Ashley





Re: Build 137

Benny Barber
 

In my testing of the quote and emoji spacing, everything worked just fine. Good work, Kosta. Thanks
Benny

On Jul 10, 2018, at 6:27 PM, FlickType <@FlickType> wrote:

Please test the new quote and emoji spacing functionality and report any unexpected behavior, ideally with a small reproducible example.

What's new:
- Crash fix

Previously:
- A space will now be inserted before the first typed emoji. No spaces will be inserted between consecutive emojis.
- Unwanted spaces around quotes will now be stripped.
- FlickType hint announcements have been limited to the first 3 times since launching the keyboard. This will reset whenever the keyboard is relaunched, which happens if you reboot your device, if you update FlickType, if FlickType crashed, or if full access is toggled in the settings. So while this won't prevent the hints entirely for those who really don't need them, it will silence them for the vast majority of the cases.

Thank you for testing FlickType!

Warmly,
Kosta and Ashley



Build 137

 

Please test the new quote and emoji spacing functionality and report any unexpected behavior, ideally with a small reproducible example.

What's new:
- Crash fix

Previously:
- A space will now be inserted before the first typed emoji. No spaces will be inserted between consecutive emojis.
- Unwanted spaces around quotes will now be stripped.
- FlickType hint announcements have been limited to the first 3 times since launching the keyboard. This will reset whenever the keyboard is relaunched, which happens if you reboot your device, if you update FlickType, if FlickType crashed, or if full access is toggled in the settings. So while this won't prevent the hints entirely for those who really don't need them, it will silence them for the vast majority of the cases.

Thank you for testing FlickType!

Warmly,
Kosta and Ashley


Re: Build 136

David Nason
 


One other issue with this build. 
 While the manual typing does seem better, I've noticed that sometimes, if for example I try to type the letter s, VoiceOver will say d as I lift my finger, but I will in fact have successfully typed the s. 
 So the accuracy is improved, but VoiceOver is giving me false information. 
 
 Dave 
 


On 10 Jul 2018, at 18:16, FlickType <hello@...> wrote:

Thank you Benny and David, got the crash reports. Looking into it.

- Kosta