paypal/paypal-android

Stuck on the web view

emartynov opened this issue · 9 comments

PayPal Android SDK Version

0.0.9

Environment

Sandbox

Android Version & Device

Any

PayPal dependencies

paypal-payments-sdk = { module = "com.paypal.android:paypal-native-payments", version.ref = "paypal" }
paypal-core-payments-sdk = { module = "com.paypal.android:core-payments", version.ref = "paypal" }

Describe the bug

Every time when I fire paypal checkout and enter email I see web view that says app id or return URL is wrong. No way I can proceed further.

iOS people are fine. Their SDK works (after they did some cache reset).

To reproduce

  1. Add paypal dependency
  2. Configure according to documentation
  3. Fire the order processin
  4. Enter email

Expected behavior

I can pay from my paypal balance.

Screenshots

No response

Exciting reply from PayPal support:

We usually advise our partners to integrate the checkout using JavaScript SDK (https://developer.paypal.com/docs/multiparty/checkout/). Would that be feasible on your end?

It looks like the only option I have now.

Hi @emartynov we appreciate the feedback and will look into this. This is for the native PayPal checkout correct? A screenshot would be most helpful here. I can forward it internally.

Thank you for the reply, here is a screenshot
Screenshot_1687272415

@emartynov thanks! Actually I misspoke, I meant to say a video if possible 🙏. Mostly trying to provide context to the team that maintains this library. Since the PayPal Native flow is highly visual, I have a feeling a video reproducing the issue may connect some dots on our end and lead to a faster fix.

There is nothing extra in video - PayPal native login and start web page that lands on the screenshot.

@emartynov understood. Still, for the record a video will help us escalate the issue.

Sure, here it is

Kapture.2023-06-22.at.14.03.35.mp4

@sshropshire this is resolved. Accidentally!

So, I've decided to try library update - the 0.0.10.
There was change - library requires client id instead of the token for the config.
However, I missed it and I was still passing the token instead. And bam - I was able to complete the flow.

Closing this and I will open couple of new one