CardEntry doesn't accept input (possible device specific issue)

[dnorvell]

Hey guys super cool library. I put it in my app and was super happy with the look/feel/experience.

However, I ran into one issue. The card entry form worked on my Google Pixel, but when I tried it on a samsung phone (Samsung Galaxy S6 samsung-sm-g920a) the card entry form refused to accept ANY sort of input.

I tried it on my friends Samsung phone (an S7) and it worked flawlessly. However, he had a custom keyboard downloaded/installed while my other phone was using the default samsung keyboard...so I think thats where the issue might be stemming from. Any idea why it wouldnt be playing nicely with your card entry form, or if there is a workaround?

I'd really like to use this control in my app, but don't feel good about pushing it to the market if this bug might unknowingly plague some of my users. Have you guys encountered this before?

Thanks for any feedback!

[aquamatt]

Hello - Thanks for your mail. I have forwarded your note to the author so he may be able to help you! Delighted that you're finding the CardEntry package useful! Regards Matthew

…

On 7 January 2017 at 00:39, dnorvell ***@***.***> wrote: Hey guys super cool library. I put it in my app and was super happy with the look/feel/experience. However, I ran into one issue. The device worked on my Google Pixel, but when I tried it on a samsung phone (Samsung Galaxy S6 samsung-sm-g920a) the card entry form refused to accept ANY sort of input. I tried it on my friends Samsung phone (an S7) and it worked flawlessly. However, he had a custom keyboard downloaded/installed while my other phone was using the default samsung keyboard...so I think thats where the issue might be stemming from. Any idea what it wouldnt be playing nicely with your app, or of a workaround? I'd really like to use this control in my app, but don't feel good about pushing it to the market if this bug might unknowingly plague some of my user. Have you guys encountered this before? Thanks for any feedback! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFxFSFFFLb_VonzcsSFKUknN56TL-wjks5rPt7FgaJpZM4LdQyE> .

-- ----- Matthew Pontefract voice: +44 7906 359 023 skype: matthewpontefract ReThought UK: +44 20 33 22 11 55 ReThought US: +1 646-461-4525 http://www.rethought-solutions.com http://about.me/matthewpontefract http://uk.linkedin.com/in/matthewpontefract GPG key ID / fingerprint: E87A3389 / 7413 275E 1044 FA9E 03EC 39BD 232A 30DB E87A 3389

[tomjhall]

Yeah it definitely sounds like a problem with the keyboard. I had encountered this earlier but thought I had nailed it. Unfortunately I don't have access to that hardware so I won't be able to reproduce - you are welcome to try and find the issue - but I suspect that even if we fixed this it may break on some other hardware.

The implementation was written as a View that was editable - ie not an override of EditText or TextView - I suspect the ultimate fix would be to override EditText and let it take care of the (potentially very complex) input differences.

I will take a look but unfortunately I'm not sure I will get to it in the next few weeks