Skip to content

Conversation

@DaVinci9196
Copy link
Contributor

No description provided.

@mar-v-in
Copy link
Member

mar-v-in commented Nov 12, 2024

Using CustomTabsIntent means moving authentication tokens and cookies into the current browser, meaning you sign in the browser into a Google account even if the user doesn't want that.

@DaVinci9196
Copy link
Contributor Author

DaVinci9196 commented Nov 13, 2024

Using CustomTabsIntent means moving authentication tokens and cookies into the current browser, meaning you sign in the browser into a Google account even if the user doesn't want that.

Yes, but during use, I found that when I jump to the web page to add a payment method and view other content, an error page will be displayed.

@mar-v-in
Copy link
Member

You mean you can't add a PayPal account inside the WebView? There is a pending TODO in WebViewHelper to redirect some navigations to the browser, I guess that's what needs to be implemented correctly. It even shows a message shortly before the PayPal screen hinting that it should open an external browser:
ef53a37_mSEyeYGtSN-W6qCjq7MLiQ

@DaVinci9196
Copy link
Contributor Author

DaVinci9196 commented Nov 14, 2024

@mar-v-in I tried to click Add PayPal in the webview and then jump to the browser for subsequent operations, but when I clicked Return to the merchant (an error pop-up window appeared with account restriction), I could not return to the page before the jump (the page in the screenshot above).

Below is the normal process after using CustomTabsIntent. They have data interaction and cannot be separated.
image
image

@DaVinci9196 DaVinci9196 deleted the fix_pay_error branch February 27, 2025 02:14
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

Successfully merging this pull request may close these issues.

2 participants