#Srujan-fetch-error
paper sparrow
I can give you as much context as you'd like. Just switched acct ids to a test account so I'm not sure if thats the issue
rotund kayak
is there any actual impact of this issue in preventing customers from paying or otherwise customer-facing errors?
Some of our libraries and hosted surfaces can print errors like this to the console due to misconfigurations on our end, or privacy-focussed browser extensions or adblockers, but it's generally something that can be ignored. The r.stripe.com domain that can't be accessed as mentioned in the log is a teritary domain we use for metric tracking for the library and is not in the critical path of any payments code so I wouldn't expect these errors to have any customer impact, but let me know if that isn't the case.
paper sparrow
Okay cool. I actually don't see the error anymore for some reason after reloading the app