Script Error on 3rd party scripts

Hi

We frequently get the dreaded "Script error" message along with a stack trace of "at ? line 0, column 0" for javascript errors logged by Raygun. We do believe these are 3rd party scripts for services that we use such as Google analytics, New Relic and Intercom.

Initially we tried suggestions in your post on the subject here: https://raygun.com/blog/2015/05/fixing-script-errors/

We can add crossorigin="anonymous" on the script tag for some scripts but others are "magically inserted" and harder to affect. Some like Google analytics does not seem have "Access-Control-Allow-Origin: *" on the response either.

Do you have any further suggestions how to approach this problem? Or is the best solution to simply ignore the errors and filter out error that does not provide relevant information?

---

Hello!

The best solution at the moment would be to ignore those errors and filter out errors that do not provide relevant information. The easiest way to do this may be to manually mark the offending errors as Permanently Ignored in the Crash Reporting dashboard or you can setup more detailed filters under Filter in the left navigation side bar (under the Crash Reporting section).

Please let us know if you have any questions, comments, or feedback!

Thank you,

Jesse, Developer Evangelist at Raygun

---