3

I have JS exception logging so I can see all the JS exceptions that are being thrown on my clients.

Very often I come across these:

Script error
http://connect.facebook.net/nl_NL/all.js:0

or just Script Error on line 0 (most likely also triggered by FB)

Anyway, my exception logs are cluttered by these exceptions, so I'm wondering:

  • Is there anything that I can do to prevent these specific errors?
  • Do the end users have active problems when these errors occur, or is this an uncritical script error on Facebooks part?
  • Is it wise to set them to ignore in my exception logger?

The errors seem to come and go pretty random, without me taking any action, but still it feels freaky to start ignoring these exceptions.

Etheryte
  • 24,589
  • 11
  • 71
  • 116
Dirk Boer
  • 8,522
  • 13
  • 63
  • 111

1 Answers1

3

I've also seen this for facebook. As I understand it, this is not a Facebook specific error - it's an origin policy error. This may occur when people visit your site without having facebook cookies, for instance (something that should be quite common and normal). This is code beyond your control - feel free to ignore the warnings being raised.

See more discussion at this excellent stack overflow post: Cryptic "Script Error." reported in Javascript in Chrome and Firefox.

Community
  • 1
  • 1
Jean
  • 670
  • 1
  • 5
  • 14
  • Thanks, following up: can I safely ignore this error forever, or could it be that there is any action that I need to take? I.e. could this also happen when I haven't upgraded through the latest SDK, or whatever? – Dirk Boer Aug 17 '14 at 15:36
  • It's weird anyway that there are errors popping up in there scripts if there are no problems. You would expect they would have handled all the errors gracefully. – Dirk Boer Aug 17 '14 at 15:37