Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Autofill from Google Payments makes the card INVALID, because of wrong formating in EXPIRATION DATE #88

Closed
pesjak opened this issue May 16, 2020 · 7 comments · Fixed by #89

Comments

@pesjak
Copy link

pesjak commented May 16, 2020

General information

  • SDK/Library version: 4.2.0
  • Android Version and Device: OnePlus 6T Android 10

Issue description

When using autofill from Google Payment, the expiration date gets wrong formatting, making the card NOT valid.
Example:
10/ /24 ---> (should be) 10 / 24

@scannillo
Copy link
Contributor

Hi @pesjak - can you include steps to help us reproduce your issue, along with screenshots of the issue you see?

@pesjak
Copy link
Author

pesjak commented May 18, 2020

I can't include the screenhost, because the phone forbides it, because it is "sensitive" screen.

Steps are:

  1. Click on the empty box, where you enter the card number
  2. (Pops up selection from autofill) Select your card
  3. Enter CVC code from that card (Google Payments Dialog)
  4. Confirm the entered code (Google Payments Dialog)
  5. Everything gets filled (Number, Date (double slashes) , CVC)

Additional:
If you click on DATE, you will get keyboard where MONTH is selected but YEAR isn't.

@sshropshire
Copy link
Contributor

Hi @pesjak are you able to take a picture of the screen with another phone?

@pesjak
Copy link
Author

pesjak commented May 18, 2020

received_1426883560824201

@sshropshire
Copy link
Contributor

@pesjak thank you. To confirm, does this issue occur in the repo's "Sample" application?

@pesjak
Copy link
Author

pesjak commented May 18, 2020

Yes, I checked thed Sample app and the issue remains.

@sshropshire
Copy link
Contributor

@pesjak awesome thank you. We are looking into this issue and will report back here when we have a solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants