You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the previous version I was using(4.13.0), error.getException() was returning the original root exception. I'd still expect that.
Observed behavior
With 4.22.3 it returns BugsnagException, where cause is the cause of the original root exception, message is the message of the original root exception, however type is BugsnagException.
Steps to reproduce
Just subclass the Exception and either throw it or call Bugsnag.notify().
Version
4.22.3 but might have been there since 4.19.1 (#576)
Additional information
For me this is a breaking change not documented properly. I do instanceOf checks of the error.getException() in BeforeNotify to prevent notifications on some exceptions. I have an interface to mark exceptions that I don't want to report (such as several API response codes) but as BugsnagException is not the implementation of that interface everything is being sent. Moreover, for handled errors I can't rely on error.getException().getCause() because there is often no cause.
The text was updated successfully, but these errors were encountered:
Expected behavior
With the previous version I was using(4.13.0),
error.getException()
was returning the original root exception. I'd still expect that.Observed behavior
With 4.22.3 it returns
BugsnagException
, where cause is the cause of the original root exception, message is the message of the original root exception, however type isBugsnagException
.Steps to reproduce
Just subclass the
Exception
and either throw it or callBugsnag.notify()
.Version
4.22.3 but might have been there since 4.19.1 (#576)
Additional information
For me this is a breaking change not documented properly. I do
instanceOf
checks of theerror.getException()
inBeforeNotify
to prevent notifications on some exceptions. I have an interface to mark exceptions that I don't want to report (such as several API response codes) but asBugsnagException
is not the implementation of that interface everything is being sent. Moreover, for handled errors I can't rely onerror.getException().getCause()
because there is often no cause.The text was updated successfully, but these errors were encountered: