-
Notifications
You must be signed in to change notification settings - Fork 42
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
PayPal native payment doesn't call listener about success #178
Comments
Hi @emartynov I'm unable to reproduce on a Pixel 6 Pro running Android 13. What kind of device (or emulator) are you using, along with OS version? I can try to replicate by aligning my environment with your setup. |
It is an API 34 emulator. Not sure if it matters. |
I was able to complete the PayPal native flow successfully on an API 34 emulator. Can you share how you're instantiating the |
@sshropshire just to confirm your flow completely replies to the callback from the client and doesn't do anything with deep link except it is mentioned in the manifest to get relaunched after the flow if needed. |
same problem , any solution for this problem @emartynov the instantiating of PayPalNativeCheckoutClient var coreConfig = CoreConfig(
payPalNativeClient.listener = object : PayPalNativeCheckoutListener {
|
Yes, there is intent back called |
thanks for reply to me ,please can you share with me the solution , with me not
return to Success call back ,it keep loading with no response and when cancel it return to cancel callback
, not open PayPal sheet
@emartynov @sshropshire
|
I have the same problem and I haven't found a solution yet |
PayPal Android SDK Version
0.0.11
Environment
Sandbox
Android Version & Device
Android 14
PayPal dependencies
implementation "com.paypal.android:paypal-native-payments:0.0.11"
Describe the bug
BTW, I see the same with 0.0.10 version.
The native Paypal client doesn't call the listener with the successful payment.
In addition, the Paypal card payment client does inform the listener about successful payment.
To reproduce
Expected behavior
Screenshots
No response
The text was updated successfully, but these errors were encountered: