Raven.min.js line 2 "undefined" error

[aariacarterweir]

Hi, getting a lot of "undefined" errors which are being caught by raven.min.js, no breadcrumbs prior to the error and no stacktrace other than it being caught by line 2 of raven.min.js. I'm running 3.26.2 of the SDK, the error seems to happen on all browsers and OSs and for some users it appears to be happening every time they load a page. No interaction with the page is recorded prior to the error being thrown. I cannot reproduce the error even if I login as the user and use the exact same OS and browser version :(

Should Sentry be getting more information for this or does the stacktrace simply just not exist?

Thanks

[aariacarterweir]

Seemed similar to #729 , but that was fixed with #872 ?

[mateusmoura]

I'm using SDK 3.23.3 and have a same error.

[kamilogorek]

It's very hard to tell without a reproduction steps to be honest. There are just too many things that can cause this. Can you post some links to mentioned events in our Sentry UI so I can take a look at them?

[aariacarterweir]

@kamilogorek thanks for looking into this, here's a link to the issue: https://sentry.io/mxstore/mxstorecomau/issues/619301480/?query=is:unresolved - is that what you need?

[aariacarterweir]

Hi @kamilogorek, sorry know you're probably really busy but wondering if you could gleam anything from the issue link I sent? :)

[kamilogorek]

New SDK has improved handling of "difficult" errors quite a bit. It'd be awesome if you could update one day and get back to me if this issue is still the case. Please feel free to reopen if it's still relevant though. Cheers!