#magepilot_error

1 messages ยท Page 1 of 1 (latest)

trail merlinBOT
#

๐Ÿ‘‹ 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.

whole jetty
cosmic tree
#

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

whole jetty
#

What version of Chrome are you using where the error is happening?

cosmic tree
#

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

trail merlinBOT
austere quest
#

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

cosmic tree
#

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

austere quest
cosmic tree
#

Yes

austere quest
cosmic tree
#

That's correct. But on older versions of Chrome it works

austere quest
#

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)

cosmic tree
#

Unfortunately it didn't resolve it

austere quest
#

Ok good to know

trail merlinBOT
austere quest
#

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?

austere quest
#

@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.

cosmic tree
austere quest
#

To clarify, "Allow sites to check if you have payment methods saved" was already enabled when you checked?

trail merlinBOT
cosmic tree
#

Yes, it was already enabled

austere quest
#

Do you have a rough timeline for when you know it worked and then when it wasnt working, for you at least?

#
stark garnet
#

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.

austere quest
#

@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

cosmic tree
#

acct_1SRyzZHLCJTKMBr3

austere quest
cosmic tree
#

No. I only see pay by link:

#

And it stopped working for me yesterday

austere quest
#

Gotcha, thanks

#

Can you get one of those example request ID from the session request?

austere quest
#

On your own page preferably, but really any such request where you would expect it to appear but it doesnt

cosmic tree
#

req_X0OqV2tFanYOOi

trail merlinBOT
trail merlinBOT
simple flint
#

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