#steph_unexpected
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1254603485769502751
๐ Have more to share? Add details, code, screenshots, videos, etc. below.
Hi, how often is that happening? Are you loading multiple Stripe Elements on your Checkout page? Can you share exact steps and your URL where I can attempt to reproduce this on my end? Do you happen to have a screen recording for when this happens?
Hi there, it does seem to be quite frequently that it is occuring although doesn't happen every time. We have both the Express Checkout Element and the Payment Element in our payment dialog. I've just managed to take a screen recording which I'll upload now
Thank you for sharing this recording. Are you able to share the URL so I can investigate this further?
Certainly, URL is https://dev.galabid.com/sports/items/89252388-daf5-4e56-b7a5-5744235a0dd2
I've created the following login which would be needed to start the purchase (otherwise any Google account):
steph+stripeuser@galabid.com
79HEx8OcNDCf!
Thank you, further looking at this.
Hmm, I'm still unable to reproduce this issue. I logged in, and have my dev console open + resizing the window. Any other tricks you used?
Ah yeah it does seem fairly intermittent, I've just tried recreating again and haven't been able to either. It seems when it does happen once you can consistently recreate it by refreshing the page but then other times it consistently works
Just had it again, this time I refreshed the page, opened the dev tools and then resized. I'm not sure if it's a consistent way to recreate though ๐
I've shared this issue with the product owning team and they will be looking into this. Can you keep the login credentials so our product engineering team can use it to attempt to reproduce the issue? This might take some time so if you're like to check on updates please write into our support with the above details.
Will do! Thank you for that