#magepilot_error
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1460632544033898683
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
๐ This usually indicates an issue with the device/browser setup, especially if the test page doesn't work. Have you gone through the steps listed here? https://docs.stripe.com/testing/wallets?ui=embedded-form#device-requirements
This is on the wallet test page, it's exactly the same as we are seeing on our production site.
Apple pay on this page works fine
As already indicated, this is no longer working for the majority of our customers. It seems to be that the ones it is still working for are on an older version of Chrome
What version of Chrome are you using where the error is happening?
I am on Version 143.0.7499.192 (Official Build) (64-bit)
I am seeing Google Pay fine on other merchants that are not using Stripe
I have another device running Chrome 139.0.7258.160 and Google Pay appears fine on that through Stripe
hey there, stepping in for dougal as they need to step away
CHecking this myself as another data point, i'm currently on the very next version (xxx.193) after the one you note and i do see google pay on our testing page
Hmm, maybe it's a problem in chrome on version xxx.192 then as I have the same issue on my mobile. A colleague is on xxx.109 and it's working fine for him
Does the buy button work for you on this page?
https://rsolomakhin.github.io/pr/gp2-test/
But on this page you do not see a google pay button? https://docs.stripe.com/testing/wallets?ui=express-checkout-element
That's correct. But on older versions of Chrome it works
Can you try resetting the service worker?
1/ Load a tab at chrome://serviceworker-internals
2/ search for "pay.google"
3/ unregister any google pay workers
4/ try the test/demo pages again
(this should not be required under any normal circumstances, just trying to see if it resolves this or not)
Unfortunately it didn't resolve it
Ok good to know
When you load your example page, can you check your chrome dev tools network tab, and find the request to https://api.stripe.com/v1/elements/sessions and share an example request-id header from the response?
@cosmic tree if you're still there can you check your chrome settings for "Allow sites to check if you have payment methods saved" being enabled?
The behaviour of this setting was set to change with Chrome 143, and could affect google pay.
Chromium developer email context: https://groups.google.com/a/chromium.org/g/paymentrequest/c/bWsk5cP3-3I/m/3PcBd7pWAAAJ
To clarify, "Allow sites to check if you have payment methods saved" was already enabled when you checked?
Yes, it was already enabled
Do you have a rough timeline for when you know it worked and then when it wasnt working, for you at least?
Let's try another surface, too. If you load this test checkout session, do you see Google Pay in the payment method list there?
https://checkout.stripe.com/c/pay/cs_test_b1L9XX49APmIum8HTlz9BkGPTAJhwyHCame50gj0910bZx6NUbBR4xPBxJ#fid1d2BpamRhQ2prcSc%2FJ1VRJVZka3YnKSdnandhYHdWcXxpYCc%2FJ2FgY2RwaXEnKSdkdWxOYHwnPyd1blpxYHZxWmFRM1xMdmFyXH1JdjRfTTMxQlFLVTdyTTU1R2o3YTZ9X1wnKSdjd2poVmB3c2B3Jz9xd3BgKSdnZGZuYndqcGthRmppancnPycmY2NjY2NjJyknaWR8anBxUXx1YCc%2FJ2hwaXFsWmxxYGgnKSdga2RnaWBVaWRmYG1qaWFgd3YnP3F3cGB4JSUl
Hi there! I'll be taking over for synthrider here. I'm happy to help continue debugging, but we do close threads for inactivity after a period of time.
@cosmic tree if you're still around, can you alternately share your account ID (acct_123) where you observe many customers seeing this behaviour? We'd like to do some analysis on our side
acct_1SRyzZHLCJTKMBr3
Anything you can say about timing, or results of trying on the checkout link i shared?
Gotcha, thanks
Can you get one of those example request ID from the session request?
this
On your own page preferably, but really any such request where you would expect it to appear but it doesnt
req_X0OqV2tFanYOOi
Hi there
I'm not sure if you're still here or not
My colleague is still working with the product team internally
I think at this point we should convert this to a support ticket
Someone from my team will take the ticket and revert back once we find something