Error message property logged as [object ErrorEvent]

[daangeerdink]

Do you want to request a feature or report a bug?
Bug.

What is the current behavior?
Sometimes (not always) the message property of the error is logged as [object ErrorEvent]. I followed the standard implementation of Raven in Angular as described here: https://docs.sentry.io/clients/javascript/integrations/angular/.

What is the expected behavior?
To see a normal error message.

Raven 3.17.0
Angular 4.3.1
Webpack build
Not using CLI
CDN version

[benvinegar]

Is there a definition of ErrorEvent somewhere in the Angular docs? Apparently this is not "inheriting" Error in the right way.

[shanesmith]

The issue could be in TraceKit's traceKitWindowOnError() method, it doesn't seem to take into account that the message argument could be an ErrorEvent (see MDN docs)

[daangeerdink]

@benvinegar There are some docs here on ErrorEvent: https://developer.mozilla.org/en-US/docs/Web/API/ErrorEvent

[rosslavery]

Affected by this too, so are these users:
https://forum.sentry.io/t/reporting-object-errorevent/1807

raven-js@3.17.0 (but has been happening for a while on older versions too)
Angular 4.x
Using CLI

[tgensol]

Same here with Ionic 3 and raven-js@3.17.0

[sod]

<script>
  undefined.foo();
</script>

^ This in your html is logged in safari via sentry as [object ErrorEvent]. Correct message would have been TypeError: undefined is not an object (evaluating 'undefined.foo').

We have an external script that injects code via script tag that tries to create an iframe, but thats blocked by safari. As the error originates from the injected script tag, sentry just reports [object ErrorEvent]

[sod]

Another error from sentry reported as just [object Event] is from the flowplayer. The flowplayer does

jQueryElement.trigger('error', [api, {code: 5}]);

You can reproduce it by embedding jQuery and just do:

$('div:first').trigger('error')

Sentry sees something like this

Sure thats not very serializable, but an error like error on element from jQuery - context <div class="foo><div class="bar" ... would be much more helpful then [object Event]

[jdelaune]

Also affected by this.

[kamilogorek]

@daangeerdink @jdelaune @rosslavery @tgensol could someone provide a the smallest possible code that could help me reproduce this?

@sod I just checked, and Safari 10.1.2 is providing correct message in the scenario that you mentioned above.

[rosslavery]

I personally can't provide a repro, because the errors are so opaque I can't discern which part of my codebase is throwing the error. I don't have any stack traces to work with, nor an error message to figure out if it's my code, or a 3rd party lib, etc.

Hopefully someone else has a simplified example they can provide, sorry I couldn't be of more assistance.

[josketres]

We are also having this problem. I have can share some data from the last 10 days (22k events of this type, 13k users). I hope it helps you to reproduce it.

[rafinskipg]

@kamilogorek We have 2 millions errors of this type. I thought it was our problem, but we were unable to track it correctly.