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
{{ message }}
This repository has been archived by the owner on Sep 14, 2020. It is now read-only.
which seems to work properly on the bugsnag site, but when I am in dev bugsnag seems to not continue executing the previous handler, and thus the regular react native error doesn't appear (and leaves the app in a inconsistent state).
Digging a bit into bugsnag library, it seems that if for some reason it doesn't need to notify to bugsnag, it just returns the notify function and doesn't call the previousHandler / postSendCallback.
Does that makes sense or is it missing the previous global handler by design?
Thanks!
The text was updated successfully, but these errors were encountered:
It seems that the ErrorUtils.getGlobalHandler is not handled properly. I have set this configuration:
which seems to work properly on the bugsnag site, but when I am in dev bugsnag seems to not continue executing the previous handler, and thus the regular react native error doesn't appear (and leaves the app in a inconsistent state).
Digging a bit into bugsnag library, it seems that if for some reason it doesn't need to notify to bugsnag, it just returns the
notify
function and doesn't call thepreviousHandler
/postSendCallback
.Does that makes sense or is it missing the previous global handler by design?
Thanks!
The text was updated successfully, but these errors were encountered: