MR 45 Hide the suggestions box when keyboard is hidden about flutter_typeahead

[KaYBlitZ]

Hi, can you post some minimal sample code that causes this error? I want to reproduce it to see what is happening exactly. For now, you can use the previous version of 1.0.2 in your pubspec until this gets resolved.

…

On Wed, Feb 20, 2019, 12:38 AM AnSLEX ***@***.***> wrote: Hello, I get a closing keyboard immediately after this change on a closed keyboard: E/SpannableStringBuilder( 9947): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length I tap on the entry field, keyboard opens and closes and I get an error. This issue appeared with this new change. OS: Android 7.1.1 Flutter version 1.2.0 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#48>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFPpTqGbtXNCBgz88vKe_X6KgD8dcKuMks5vPN9IgaJpZM4bEcr2> .

[sjmcdowall]

Also what platform (iOS/Android) and steps to reproduce -- Also maybe your full code -- maybe something else in the Widget tree is interfering ?? And finally -- how about a stack trace that shows the error (may give a clue exactly where the issue is)..

…

On Feb 20, 2019, at 7:00 AM, Kenneth Liang ***@***.***> wrote: Hi, can you post some minimal sample code that causes this error? I want to reproduce it to see what is happening exactly. For now, you can use the previous version of 1.0.2 in your pubspec until this gets resolved. On Wed, Feb 20, 2019, 12:38 AM AnSLEX ***@***.***> wrote: > Hello, > > I get a closing keyboard immediately after this change on a closed > keyboard: > E/SpannableStringBuilder( 9947): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot > have a zero length > > I tap on the entry field, keyboard opens and closes and I get an error. > This issue appeared with this new change. > > OS: Android 7.1.1 > Flutter version 1.2.0 > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#48>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AFPpTqGbtXNCBgz88vKe_X6KgD8dcKuMks5vPN9IgaJpZM4bEcr2> > . > — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#48 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB8M7frQfgKQSFRJL2SW_1YOJ9OQ2fMtks5vPTjTgaJpZM4bEcr2>.

[KaYBlitZ]

@sjmcdowall I just took a look at the code again. I didn't test my code fully and it's causing all these issues. I just realized that if the user is using a hardware keyboard, they will not even be able to type because the code will not detect a keyboard and unfocus the focusnode. Not sure what the root cause is for these other issues people are having, but the problem code either has to be removed or changed.

It doesn't seem possible at all to detect keyboard state changes entirely in flutter code (which is what I tried doing & why we are having these issues), so we will have to use that 3rd party library which uses native code for detection.

What do you think?

[sjmcdowall]

OK -- let's use the 3rd party .. now.. how do I UNPUBLISH something .. doh!

Guess I need to get the master @ 1.0.2 and then publish again ..

[KaYBlitZ]

I am going to let @AbdulRahmanAlHamali decide whether to proceed with using the 3rd party or not. It's a pretty big change.

[sjmcdowall]

If we don't use the 3rd party -- how are we going to fix the issue?

[AbdulRahmanAlHamali]

Hello guys

Sorry for taking this long to reply. Thank you for all the hard work that you have been doing. The package would definitely be dead without your help!

Regarding the 3rd party library. I don't mind using it as long as:

1- It is good, stable, and solves the problem at hand.
2- It does not include other unneeded dependencies that we are not sure why they are there.
3- We lock the dependency to a specific version, and only upgrade to a newer version after making sure the newer version does not break our code.

So if that plugin solves the keyboard problem, which has been a huge pain in a variety of ways, then I say let's definitely go for it!

[KaYBlitZ]

I am working on incorporating the 3rd party library now and seeing if I can fix various other issues. Closing because the offending code has been removed.