#josh-unger_unexpected
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/1506042392309006356
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
taking a look, thanks for the console logs.
could you dump the full logs here as text?
Access to fetch at 'https://r.stripe.com/b' from origin 'https://js.stripe.com' has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header contains multiple values 'https://js.stripe.com, https://js.stripe.com', but only one is allowed. Have the server send the header with a valid value.
POST https://r.stripe.com/b net::ERR_FAILED 200 (OK)
(anonymous) @ js.stripe.com/v3/fin…f1178187c6d892.js:1
e @ js.stripe.com/v3/fin…f1178187c6d892.js:1
p @ js.stripe.com/v3/fin…f1178187c6d892.js:1
value @ js.stripe.com/v3/fin…f1178187c6d892.js:1
value @ js.stripe.com/v3/fin…f1178187c6d892.js:1
value @ js.stripe.com/v3/fin…f1178187c6d892.js:1
value @ js.stripe.com/v3/fin…f1178187c6d892.js:1
value @ js.stripe.com/v3/fin…f1178187c6d892.js:1
(anonymous) @ js.stripe.com/v3/fin…f1178187c6d892.js:1```
Thank you!
It looks like this is being investigated internally as we speak and they've identified the change that is causing these errors. Seems they're working on reverting this change now.
I believe they're related to analytic events and hopefully shouldn't be causing any issues with your integration.
You can probably ignore these for now, and I'd expect they should subside here shortly. If they do not, please don't hesitate to let us know !
Ok thanks do you have a link I can follow?
I don't think there's anything external facing at the moment as it relates to this.
Ok thought I'd ask
Usually if there is an incident that would break functionality we'd send comms to inform those impacted. I think in this case we just broke our own analytics with out any other impact to users integrations.
No worries, I can understand being curious and wanting to be able to follow up.