magius_error | Stripe Developers | Page 1

solar sluiceBOT Jan 27, 2025, 11:13 AM

#

👋 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/1333394401652772904

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

#

graceful badger Jan 27, 2025, 11:16 AM

#

👋
I'm not aware of something like this honestly, but this seems very isolated.

#

This happened only once ?

ebon harness Jan 27, 2025, 11:18 AM

#

The individual customer seemed to be running into this reproducibly (in both places they're able to start that form) but it's just the one customer (on I believe the one device)

graceful badger Jan 27, 2025, 11:21 AM

#

Have you tried to gather the device infos and tries to reproduce on test mode ? What browser? What SDK?...

ebon harness Jan 27, 2025, 11:24 AM

#

I'll go collect the missing info now
I know it's Chrome on Windows

but I think some of the errors might be red herrings, caused by the fact that our support handler is trying to reproduce using that customer's account in a different locale, which means the request is being routed to a different stripe account (historical reasons etc etc)

#

so I'll filter out any problems that are caused by our attempt to reproduce the problem rather than the customer's actual error...

graceful badger Jan 27, 2025, 11:31 AM

#

Yes and please collect/share any requestid you may have.

solar sluiceBOT Jan 27, 2025, 11:54 AM

#

ebon harness Jan 27, 2025, 11:54 AM

#

Got more info now: I'm sorry to have wasted your time but I think the issue was due to mismatching locales for the customer as well

It looks as though the flow was: trying to create a SetupIntent in the wrong locale, which blows up (for known reasons) and then the support agent generated the "Could not retrieve elements store due to unexpected error" response by tapping the 'submit' button on the form anyway

#

So I think this error is an edge case caused by calling 'confirmSetup' with a malformed elements object (which we ought to defend against by disabling our 'submit' button whenever that happens

sage moss Jan 27, 2025, 11:58 AM

#

False alarm then?

#magius_error