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

Incorrect Android Pay onCancel callback behaviour #145

Closed
RadoslawHardyl opened this issue Apr 11, 2017 · 2 comments
Closed

Incorrect Android Pay onCancel callback behaviour #145

RadoslawHardyl opened this issue Apr 11, 2017 · 2 comments

Comments

@RadoslawHardyl
Copy link

Hey guys,

We're using latest SDK ver 2.5.1, and we find strange BraintreeFragment behaviour connected with Android Pay(integration with AndroidPayActivity).
Basically if you start Android Pay flow twice, and in second try you will just close Android Pay Activity(e.g. back button),
instead of "onCancel" callback, you will get success callback with nonce generated in first try.

steps to reproduce:

  1. start Android Pay Activity AndroidPay.requestAndroidPay(fragment,...);
  2. select AP card and confirm
  3. receive Android Pay nonce
  4. start Android Pay Activity
  5. tap back button(close Android Pay Activity)

AC:
onCancel callback is launched

Actual Results:
onPaymentMethodNonceCreated is launched with AP nonce from point 3.

Best
Radek

@sdcoffey
Copy link

Hey @RadoslawHardyl

Thanks for submitting this bug report. It's been a week since you've submitted this issue, so I wanted to follow up and see if you were still running into it. I was not able to reproduce in our demo app using the version you provided. If this is still happening for you, let me know and we can debug from there.

@sdcoffey
Copy link

Hey @RadoslawHardyl,

I'm going to close this issue due to inactivity. Feel free to open a new issue if you're still experiencing this behavior.

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

No branches or pull requests

2 participants