Closed dkfl1995 closed 3 years ago
Yes found same issue in android only.Have you found any solution for it?
@krupalikevadiya actually, having a talk with PayPal development team so they researching this issue. Once I will get any response, will write right there
Are there any kind of news about this issue?
@valerio-fornace There's an open MR that needs a tweak but it should be ready to go after that. If I don't get a response for a few days I'll finish up the fix and do a release
@nzankich thanks this is a good news!
fixed on 4.0.1
be sure to follow the upgrade instructions for 4.0.0 https://github.com/smarkets/react-native-paypal/releases/tag/4.0.0
@nzankich still getting same issue in android.
"react-native": "0.64.2",
"react-native-paypal": "4.1.0",
Hi guys. Few days ago started with upgrading BT SDK from 2.17 to latest 3.14.2 as faced Google Play team warning like related to this issue. Found really disgusting issue right there then after upgrading. If you use like new 3.14.2 BT SDK version promise on
requestOneTimePayment
native method still remains the same each time you trigger this method. This lead to promise to be useless as it won't runresolve
orreject
on second request and then. HashCode of promise still remains the same. As on BT SDK v2.17 promise has different HashCode each time you triggerrequestOneTimePayment
method.