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

PayPal redirection is blocked by a browser dialog with alert message #611

Open
Hector1990 opened this issue Oct 20, 2022 · 4 comments
Open

Comments

@Hector1990
Copy link

General information

  • SDK/Library version: 4.17.0
  • Environment: Production and Sandbox
  • Android Version and Device: Oneplus 7 pro with Android 12 (Huawei devices or some devices without Chrome browsers)
  • Braintree dependencies:
    • com.braintreepayments.api:data-collector:4.17.0
    • com.braintreepayments.api:paypal:4.17.0

Issue description

In normal cases, when the user completes the payment behavior, it will be redirected to the product app automatically.

But on some devices, there will be a dialog blocking the redirection behavior. You can see the video. We believe that will be a big effect on the user experience. Is there any way to prevent this?

paypal_braintree_dialog_block_no_action.mp4
@sshropshire
Copy link
Contributor

Hi @Hector1990 thanks for using our SDK. This seems like a security dialog presented by the OnePlus browser. Very similar to how iOS does it as well.

If the user selects "Open" does it work as expected?

@Hector1990
Copy link
Author

@sshropshire Hi, it works as expected as the user selects "Open". But some users maybe don't notice it. And from the data we track, this amount is not low.

We also integrated PayPal through Adyen previously, they provided a redirect URL so that we can open PayPal in the webview inside our app. It works fine.

So, could you open PayPal in the webview instead of the browser?

@sshropshire
Copy link
Contributor

@Hector1990 understood. I believe the original reason why we chose to open via Chrome Custom Tabs / Browser is because of an InfoSec requirement. It is unfortunate but it may be the behavior of that particular browser. Is this reproducible with Chrome?

Otherwise, the only thing I can think of that may help is if we provide support for Android App Links. It does require more setup on the merchant side, so we haven't considered this yet. It may be something for us to look into and get prioritized.

@Hector1990
Copy link
Author

@sshropshire Thanks a lot! I believe it will be a great help to us.

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