Date   
Re: Flicktype makes Whatsapp crash!

Jean-Philippe Rykiel
 

hello again.
It seems to happen only when trying to send a message to a WhatsApp group, not to a single person. I can't see why that would make a difference, but it does on my phone.
Cheers,
JPR

Re: Flicktype makes Whatsapp crash!

Sy Hoekstra
 



I'm having the exact same problems on my iPhone 7 running iOS 11.4 and the most recent FlickType beta 


On Jul 15, 2018, at 11:04, Jean-Philippe Rykiel <jprykiel@...> wrote:

hello again.
It seems to happen only when trying to send a message to a WhatsApp group, not to a single person. I can't see why that would make a difference, but it does on my phone.
Cheers,
JPR

Feedback

Gaurav Jhunjhnuwala <gauravjj@...>
 

Hello,

I am an avid user of flick type keyboard. I really like the app and I would like to give the following feedback to help enhance the experience.

Please keep in mind that I am not fully blind but have partial vision.

Color Settings:
Visually Impaired persons have different preferences as to what color combinations are more comfortable for them to view. The app should have an option to change the color combinations for the keyboard.
I personally prefer a black background with white text so as to reduce glare. Hence I keep my iOS devices on Invert Colors mode. However since the original color of flick type is Black Background with white text, with invert colors mode enabled the flick type keyboard appears with white background and black text.
I also know of a few of my visually impaired friends who are facing the same challenge. This is by far the most high priority of all the feedback i am providing.

Viewable Letters:
While tap typing, it is sometimes difficult for visually impaired persons to make a guess as to where certain letters may lie. Currently the keyboard letters are only viewable when a user drags their finger around the keyboard, and not while tap typing mode. Perhaps the following options could be explored:
1. An option to allow the user to always see the keyboard letters regardless of whether they are tap typing or if they are touch typing
2. Option to have only a few letters visible while tap typing (perhaps only the letters in the middle row. Being able to see the letters in this row allows users to infer where desired letters in the top and bottom row may lie without having to have them shown on the screen)

Half Screen Keyboard:
All other keyboards only take up half the screen so that the top of the screen continues to be viewable.

Thank you and hope to see these changes in the near future.

Regards,
Gaurav

Re: an alternative to half size keyboard

Jean-Philippe Rykiel <jprykiel@...>
 

I sometimes have strange issues when dismissing the keyboard or switching to another one.

When dismissing the keyboard, it happens that the last lines of what I typed before is deleted, and when switching keyboards, it sometimes opens the control centre. I'm using an iPhone seven with last iOS 11, not quite sure what is happening.

Best,

JPR


http://jeanphilipperykiel.com
http://soundcloud.com/ryksounet
http://twitter.com/ryksounet
http://facebook.com/jeanphilipperykiel
Le 14/07/2018 à 20:29, Harry Bell via Groups.Io a écrit :


Yes, I agree! What I am grateful for in this keyboard is the way it makes it so easy to type chunks of text of some length. I'm really fine with changing to the iOS keyboard every now and then for something specific. 
Regards
 Harry 

On 14 Jul 2018, at 18:02, Chuck Dean <cadean329@...> wrote:


Hello, 
 As I understand it, the half screen keyboard poses many problems and the final product may not be the total solution you are waiting for. 
 Those of us who use fleksy understand typing in a text field makes VoiceOver have delays and stuttering speech, which is very annoying. So, the current thought is there will be a half screen keyboard useful to interact with the various areas of the screen, but you will want to change to the full screen keyboard to enter the bulk of your text. This seems to be the best compromise that Kosta can implement. 
 
 There has been a Couple of attempts released to the alpha group which didn't perform as expected. Kosta is a steely eyed app developer, so whatever he finally releases will be the very best app possible. 
 
 I was one of the big supporters of the half screen keyboard, at first, but since I have been using the current version of FlickType I really have no problems switching between the full screen FlickType keyboard and the iOS keyboard. 
 In my opinion the half screen keyboard will be nice., But not necessary. 
 
 Chuck 

On Jul 14, 2018, at 7:48 AM, Peter Torpey <ptorpey00@...> wrote:

I personally can't wait until the half size keyboard is available.  This would hopefully work more like the standard keyboard in that one could easily view one's text entry, navigate the cursor for editing and making corrections, etc.  As noted on this forum, there are several circumstances where dismissing the keyboard leads to a result in which the user must go back to the standard keyboard.  I'm thinking of the situation of trying to use auto-correct when sending e-mail or text messages.

This will be a welcome addition and obviate the need for switching keyboards.

--Pete

Re: an alternative to half size keyboard

Piano Geek
 

I agree with JPR on this.



~ “Ah, music. A magic far beyond what we do here. “. Albus Dumbledore

On Jul 14, 2018, at 2:52 AM, Jean-Philippe Rykiel <jprykiel@...> wrote:

Hi all,

half size keyboard might be good, I don't know how it will feel like, but in the meantime I just had an idea that I wanted to share with you.

For the moment, while flick type keyboard is on, the rotter gesture does not do anything. Why not use this rotter to temporarily dismiss the keyboard and go back to iOS edit features, until you touch the keyboard zone again?

What do you say?

Best regards,

JPR


--
http://jeanphilipperykiel.com
http://soundcloud.com/ryksounet
http://twitter.com/ryksounet
http://facebook.com/jeanphilipperykiel



Re: Flicktype makes Whatsapp crash!

 

We are currently investigating the WhatsApp crash. This is a problem with WhatsApp and not FlickType, but we are looking for possible workarounds regardless. Thank you for your patience.

- Kosta

Re: Feedback

 

Thank you Guarav,

For the Invert Colors mode, this is a known issue and we may add a different color scheme in the future. However, if you use the Smart Invert setting of iOS, things should look as expected. Please let us know if Smart Invert does not work for you for any reason.

We will soon add a setting to always show all buttons on the keyboard.

For the half-screen mode, this is something we're working on.

Warmly,
Kosta

Re: an alternative to half size keyboard

 

Yes, if you bring up the control centre you are definitely starting your initial touch way to low. It is not necessary to do this in Flicktype, starting up higher and swiping up works just as well and it won’t bring up the control centre.

 

From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of Chuck Dean
Sent: Sunday, July 15, 2018 12:35 AM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] an alternative to half size keyboard

 

 

Hello, 

 When doing the flick up and hold gesture to switch to the iOS keyboard, be sure to start the gesture about an inch above the bottom of the iPhone. This will prevent accidentally engaging the control panel. 

 Chuck 


On Jul 15, 2018, at 12:03 AM, Jean-Philippe Rykiel <jprykiel@...> wrote:

But these two buttons act strangely sometimes.
When dismissing the keyboard, it happens that last lines of text are deleted, and when switching keyboards, it sometimes opens the control
centre. I'm using an iPhone seven with last iOS 11, not quite sure what is happening.

Best,

JPR

Re: an alternative to half size keyboard

Jean-Philippe Rykiel <jprykiel@...>
 

sorry, this message was sent twice by mistake.

Cheers,

JPR


http://jeanphilipperykiel.com
http://soundcloud.com/ryksounet
http://twitter.com/ryksounet
http://facebook.com/jeanphilipperykiel
Le 15/07/2018 à 22:27, Sieghard Weitzel a écrit :

Yes, if you bring up the control centre you are definitely starting your initial touch way to low. It is not necessary to do this in Flicktype, starting up higher and swiping up works just as well and it won’t bring up the control centre.

 

From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of Chuck Dean
Sent: Sunday, July 15, 2018 12:35 AM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] an alternative to half size keyboard

 

 

Hello, 

 When doing the flick up and hold gesture to switch to the iOS keyboard, be sure to start the gesture about an inch above the bottom of the iPhone. This will prevent accidentally engaging the control panel. 

 Chuck 


On Jul 15, 2018, at 12:03 AM, Jean-Philippe Rykiel <jprykiel@...> wrote:

But these two buttons act strangely sometimes.
When dismissing the keyboard, it happens that last lines of text are deleted, and when switching keyboards, it sometimes opens the control
centre. I'm using an iPhone seven with last iOS 11, not quite sure what is happening.

Best,

JPR


Entering searches and websites

Ken Clarkg
 

For a website touch type the complete address with no flicks to the right just add a new line, that acts like fitting a go button. Now for a search just type in your word or words don't flick right after the last word just ass a new line and that's like hitting the go button.

Re: an alternative to half size keyboard

Jack Mitchell
 

I'm now subscribed to the list.  How do I get added to the Beta in test flight?

Jack Mitchell


On Sun, Jul 15, 2018 at 6:10 PM Jean-Philippe Rykiel <jprykiel@...> wrote:

sorry, this message was sent twice by mistake.

Cheers,

JPR


http://jeanphilipperykiel.com
http://soundcloud.com/ryksounet
http://twitter.com/ryksounet
http://facebook.com/jeanphilipperykiel
Le 15/07/2018 à 22:27, Sieghard Weitzel a écrit :

Yes, if you bring up the control centre you are definitely starting your initial touch way to low. It is not necessary to do this in Flicktype, starting up higher and swiping up works just as well and it won’t bring up the control centre.

 

From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of Chuck Dean
Sent: Sunday, July 15, 2018 12:35 AM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] an alternative to half size keyboard

 

 

Hello, 

 When doing the flick up and hold gesture to switch to the iOS keyboard, be sure to start the gesture about an inch above the bottom of the iPhone. This will prevent accidentally engaging the control panel. 

 Chuck 


On Jul 15, 2018, at 12:03 AM, Jean-Philippe Rykiel <jprykiel@...> wrote:

But these two buttons act strangely sometimes.
When dismissing the keyboard, it happens that last lines of text are deleted, and when switching keyboards, it sometimes opens the control
centre. I'm using an iPhone seven with last iOS 11, not quite sure what is happening.

Best,

JPR


--
Jack Mitchell
Durham, NC

Re: Flicktype makes Whatsapp crash!

Jean-Philippe Rykiel
 

Hey Kosta.

If it's a WhatsApp issue, is there a way to tell them about it? They have a support page, but how can we explain them what's happening technically speaking, since it only happens with flick type?

best,

JPR


http://jeanphilipperykiel.com
http://soundcloud.com/ryksounet
http://twitter.com/ryksounet
http://facebook.com/jeanphilipperykiel

Le 15/07/2018 à 20:26, FlickType a écrit :
We are currently investigating the WhatsApp crash. This is a problem with WhatsApp and not FlickType, but we are looking for possible workarounds regardless. Thank you for your patience.

- Kosta


Re: Flicktype makes Whatsapp crash!

George Cham
 

I've been using what's app. And have had no crashes. Could the issue be with a older I device with a slower processer? I've using I phone 8.

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: hello@flicktype.groups.io <hello@flicktype.groups.io> on behalf of Jean-Philippe Rykiel <jprykiel@...>
Sent: Monday, July 16, 2018 5:41:35 PM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Flicktype makes Whatsapp crash!
 
Hey Kosta.

If it's a WhatsApp issue, is there a way to tell them about it? They
have a support page, but how can we explain them what's happening
technically speaking, since it only happens with flick type?

best,

JPR


http://jeanphilipperykiel.com
http://soundcloud.com/ryksounet
http://twitter.com/ryksounet
http://facebook.com/jeanphilipperykiel

Le 15/07/2018 à 20:26, FlickType a écrit :
> We are currently investigating the WhatsApp crash. This is a problem with WhatsApp and not FlickType, but we are looking for possible workarounds regardless. Thank you for your patience.
>
> - Kosta
>
>
>
>




Punctuation preference

Jean-Philippe Rykiel
 

Hi there,

I've asked this question before but didn't have any feedback.

How many of you would like to have the comma , Sign appear before the period sign in the punctuation list? I seem to use comma more frequently, am I the only one? I think it would be nice to have a Choice. What do you say?

Best regards,

JPR


--
http://jeanphilipperykiel.com
http://soundcloud.com/ryksounet
http://twitter.com/ryksounet
http://facebook.com/jeanphilipperykiel

Re: Punctuation preference

Jean-Philippe Rykiel
 

Or, maybe, have the comma Appear first, and the new line gesture insert a period?

JPR


http://jeanphilipperykiel.com
http://soundcloud.com/ryksounet
http://twitter.com/ryksounet
http://facebook.com/jeanphilipperykiel

Le 16/07/2018 à 09:46, Jean-Philippe Rykiel a écrit :
Hi there,

I've asked this question before but didn't have any feedback.

How many of you would like to have the comma , Sign appear before the period sign in the punctuation list? I seem to use comma more frequently, am I the only one? I think it would be nice to have a Choice. What do you say?

Best regards,

JPR

Re: Punctuation preference

Shawn Krasniuk
 

I use the period symbol more than the comma symbol so that would be inconvenient for me. I don't mind swiping down to get a comma but to each his own I guess. Anyway, Kosta will have the final say so I'll support whatever he decides. This has become my favorite app.

On Jul 16, 2018, at 2:46 AM, Jean-Philippe Rykiel <jprykiel@...> wrote:

Hi there,

I've asked this question before but didn't have any feedback.

How many of you would like to have the comma , Sign appear before the period sign in the punctuation list? I seem to use comma more frequently, am I the only one? I think it would be nice to have a Choice. What do you say?

Best regards,

JPR


--
http://jeanphilipperykiel.com
http://soundcloud.com/ryksounet
http://twitter.com/ryksounet
http://facebook.com/jeanphilipperykiel



Possible compromise

Morzorak@...
 

How about if they make it so that when you swipe right it brings up the punctuation based on a custom field like the emoji? Then like the emoji you can select which symbols are available and in which order. Put your period, comma, or even hashtag first as you prefer.

Re: Possible compromise

Ken Clarkg
 


 That sounds the best way, because why mesh it up for others. And really it's not hard to do its only one flick down. 


On Jul 16, 2018, at 9:08 AM, Morzorak via Groups.Io <Morzorak@...> wrote:

How about if they make it so that when you swipe right it brings up the punctuation based on a custom field like the emoji? Then like the emoji you can select which symbols are available and in which order. Put your period, comma, or even hashtag first as you prefer.

Re: Possible compromise

 

I hope the period remains as it is. After all a double press of the spacebar using the iOS keyboard also inserts a period and nobody is asking Apple to change it to a comma. I assume that strictly from a statistical point of view the period is used more in most western languages than the comma and therefore it is what the default is.

 

In the above paragraph I ended the three sentences with a period, but didn’t need to use a single comma. In this last sentence one comma was used.

 


Best regards,

Sieghard

 

From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of Morzorak via Groups.Io
Sent: Monday, July 16, 2018 7:08 AM
To: hello@flicktype.groups.io
Subject: [FlickType] Possible compromise

 

How about if they make it so that when you swipe right it brings up the punctuation based on a custom field like the emoji? Then like the emoji you can select which symbols are available and in which order. Put your period, comma, or even hashtag first as you prefer.

WhatsApp crash update: important information

 

We have now determined that the issue lies purely within WhatsApp and their recent update a couple of weeks ago. To help us resolve the issue, please file a bug report with them using the below template. The more people file the bug, the sooner the issue will be resolved. To submit a bug report, open up WhatsApp, go to Settings, Help, Contact Us. Paste the text from the template below into the textfield, and then tap Next at the top right. You might then be presented with a list of questions that WhatsApp thinks are relevant to your inquiry. Ignore those and select "This does not answer my question" at the very bottom of the screen. This will pop up an email ready to be sent to the WhatsApp support address. Make sure the composed email includes the entirety of the template text and optionally include somewhere a date and time of the last couple of times the app crashed. Template text follows below:

---

Dear WhatsApp support team,

Since version 2.18.71.6, I have been experiencing a WhatsApp crash that is preventing me from using your app in conjunction with the FlickType keyboard. FlickType is a keyboard for blind and low-vision VoiceOver users like myself, and unlike most other keyboards, it takes up the entire screen when it pops up. The crash occurs as soon as the keyboard pops up in a conversation textfield, and following their own investigation, the FlickType developers believe that it is the full-screen aspect of the keyboard that indirectly causes WhatsApp to crash (FlickType itself is not crashing). Please note that the problem does not always happen, and seems to be more likely to happen on threads with a lot of messages, as opposed to threads with only a handful of messages.

While there are no steps that can reliably reproduce the issue, below are some technical details from the Flicktype developers that might assist you in addressing the problem:

> 1. All collected WhatsApp crash logs from our users follow the same pattern, where a layout operation triggers a subsequent layout operation ad infinitum, until the stack space (approximately 512 invocations) is exhausted and the WhatsApp terminates with a segmentation fault.
2. The last part of the stack trace is not always the same, but is almost certainly unrelated to the cause of the crash.
3. A sample crash log (unsymbolicated) can be found here: https://github.com/keleftheriou/FlickType/blob/5ef1a5a9e0666e0869edc3426389b929400822d4/tmp/WhatsApp-2018-07-12-173526.ips.crash
4. The above crash log, partially symbolicated to show UIKit and other system calls can be found here: https://github.com/keleftheriou/FlickType/blob/5ef1a5a9e0666e0869edc3426389b929400822d4/tmp/WhatsApp-2018-07-12-173526.ips-PARTIALLY-SYMBOLICATED.crash
5. A sample WhatsApp log with multiple `chatmsgs//preserve-scroll-position/failed: empty table` entries right before the crash can be found here: https://github.com/keleftheriou/FlickType/blob/8a309244bde6c02d3101846a85e126a30f4fb057/tmp/whatsapp-2018-07-15-16-21-49-628-WhatsApp-87-launch-CRASH-redacted.log
6. We are more than happy to help in any way we can. We can be reached at @FlickType and answer any additional questions you might have to help resolve the issue as quickly and as easily as possible.
Thank you for your time, and I'm really looking forward to being able to use WhatsApp with FlickType again!

Warmly,
A VoiceOver WhatsApp user.