Set handled/unhandled state

Currently there is no easy way to set the handled/unhandled state for an error. This makes the stability score useless to us.

In our JS app we are catching all exceptions, for logging + sending to Bugsnag. While we do “handle” the exception, in the sense that we’re catching it, the user will see an error message.

So, from a stability perspective it wasn’t handled. Thus, we’d like these errors to worsen the Bugsnag stability score. And for that to work we’d like to set the handled/unhandled state via notify.

See similar issue for ruby: https://github.com/bugsnag/bugsnag-ruby/issues/549

[johnkiely1]

Hi @sandstrom,

Nothing new to report on timeframes on this yet. We are still looking to address this across all of our platform specific notifiers which makes this a bigger piece of work to implement. Other priorities have meant this has slipped somewhat. Updates will be added here when we have them.

[sandstrom]

Awesome! 🎉 Tried it just now, works great!

Would still expect the latest release to be available in NPM, even though all bug fixes therein only pertain to certain platforms.

---

Somewhat related (since it affects session counting and stability scores, which this is related to):

uBlock seems to be blocking Bugsnag.

1. Would it be possible for us to send “a user was active and this is the user agent string, ip, etc” request from our backend, for tracking ‘user stability’. That way we wouldn’t be affected by session tracking being blocked? Something you have thought of or discussed internally?

2. Ideally we’d also pipe error reports through our backend, since those are being blocked too.

Stability score is less useful if ~30% of users aren’t included (due to ad blockers).

Opened an issue about it: https://github.com/bugsnag/bugsnag-js/issues/1228