You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SDK/Library version: 1.33.7, 1.34.0 and previous versions
Environment: Both
Browser and OS: Affects 158 of our users in the last week, across all browsers, especially Safari and Mobile Safari
Issue description
Something within Google's pay.js is throwing an exception. However, because of CORS rules, (ie. the script is not being loaded with the crossorigin='anonymous' attribute, our crash reporting tools do not have access to the exception or to the stack trace.
It only shows in those systems as "Script error in pay.js".
Workarounds would be to load the scripts within the element, and set this flag ourselves, but it slows down the initial load of the page.
Or, we could compile our own version of the dropin, but we'd be required to re-build with every update.
Both of these have their downsides, and I think the best way is to resolve this in the component itself. It also makes addressing the root cause of the under-the-hood issue easier to resolve for others who are using crash reporting tools.
General information
Issue description
Something within Google's pay.js is throwing an exception. However, because of CORS rules, (ie. the script is not being loaded with the
crossorigin='anonymous'
attribute, our crash reporting tools do not have access to the exception or to the stack trace.It only shows in those systems as "Script error in pay.js".
A solution to this is available within Raygun's documentation, but because scripts are loaded on-demand from within the dropin component, we are not able to make this change.
https://raygun.com/documentation/language-guides/javascript/crash-reporting/script-errors/
Both of these have their downsides, and I think the best way is to resolve this in the component itself. It also makes addressing the root cause of the under-the-hood issue easier to resolve for others who are using crash reporting tools.
A PR is available with our suggested remedy:
#865
The text was updated successfully, but these errors were encountered: