-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some uncaught exceptions just show generic RuntimeException
instead of the root cause
#171
Comments
Thanks for the report, @edenman. There is a lot of options here. Potentially we could mark reflection exception frames as not likely being the root cause, which would then surface the NPE in this particular case. 🤔 Might have to think about this one more to determine the general case. |
InvocationTargetException always wraps another exception (potentially
recursively, as evidenced by the included trace) as a result of reflective
invocation, so not including it as a potential cause would be a welcome
improvement.
…On Fri, Aug 4, 2017 at 7:35 PM Delisa Mason ***@***.***> wrote:
Thanks for the report, @edenman <https://github.com/edenman>. There is a
lot of options here. Potentially we could mark reflection exception frames
as not likely being the root cause, which would then surface the NPE in
this particular case. 🤔 Might have to think about this one more to
determine the general case.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#171 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAEEEcghEtcDVDCpd3E3brQPq-yYoOm_ks5sU6rLgaJpZM4OqbTD>
.
|
That makes sense to me. Thanks, @JakeWharton. |
Update for visibility: The change is something we should make during event processing, rather than have the client process and discard exceptions or stack frames. Investigating how we should detect and better surface the underlying exception. |
Update plugin to extract SO files from transitive dependencies
I'm migrating to Bugsnag and I'm a bit disappointed by the detail raised in this issue.
In case you can't see that link:
What's weird is that other issues display the root cause just fine. Is there a setting that I can use to control which exception is displayed at the top level?
The full stacktrace of the first issue:
The text was updated successfully, but these errors were encountered: