You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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:
AndroidPay.requestAndroidPay(fragment,...);
AC:
onCancel callback is launched
Actual Results:
onPaymentMethodNonceCreated is launched with AP nonce from point 3.
Best
Radek
The text was updated successfully, but these errors were encountered: