#intelagent_api
hybrid spireBOT
đ 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/1327367184091054122
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
fossil pebble
This is the visual I've received from a few customers. I understand this may not be the proper place to discuss something like this, and would be happily pointed in the right direction.
floral hawk
Hi, as long as the questions/ screenshots do not include PII information we are happy to help here.
fossil pebble
They do not contain PII
floral hawk
Can you say more? How can I repdocude this on my end using the URL you shared? Does this happen everytime?
fossil pebble
Then. select a few adults / children to make the payment elements render below. It's not happening every time, and is only happening very occasionally. I haven't even been able to reproduce but have heard from several of our clients customers that they are having this problem.
I am dead lost on how to possibly debug this, which is why I reached out here
hybrid spireBOT
floral hawk
It would be hard to debug if neither of us can reproduce this. I doubt someone looked in the developer console to see if there is any errors
fossil pebble
Right, and these were on mobile too :/
Is it possible a transient stripe-side error would produce a result like this? Or is this not a failure mode at all for y'all?
floral hawk
Do you happen to have a Payment Intent id from one of these failures?
dapper gust
Do you know what browser the user is using in that screenshot? It looks like it may be a webview in an Android app?
fossil pebble
I am double checking to ensure I have full details on this, but I believe this was before the checkout and subsequent payment intent was evene created on our backend. This was on initial load of the checkout page I believe.
Should have the browser information in a couple of minutes or so. Apologies for not coming with more information...
The browser is just Google Chrome on Android
dapper gust
No worries, totally get it. Also do you know around when your users started reporting this? I can look in to whether we're seeing broader reports of this issue
fossil pebble
That would be much appreciated. 12:14 ET is first report
dapper gust
Not seeing another report at the moment. Testing in some Android Chrome browsers myself to see if I can reproduce
Do you know if users that see this will consistently see this, or if it goes away on a reload?
fossil pebble
Users clearly stated to us that it was transient. Multiple saying it went away the second load
Appreciate you taking the time to try to run this down.
dapper gust
Unfortunately haven't found other reports like this and I haven't been able to reproduce.
Trying to think of what else can help look in to this. It could be helpful to add some code to report javascript errors to your server to see if you can catch what this is, but I can imagine that that might not be a minor change and it may be hard to differentiate errors that came from this break vs anything else happening on the page.
https://www.geeksforgeeks.org/how-to-catch-all-javascript-errors-and-send-them-to-server/
