Closed ekuleshov closed 2 months ago
hi we have multiple onError
handlers from which the flutter framework reports errors, but some errors that we receive directly from the framework don't have a stacktrace attached so we try to capture it ourselves with a Stacktrace.current
. that's why you see getCurrentStackTrace at the very top.
And it seems like this is in some cases not sufficient enough/doesn't give enough context, in your case it was the PlatformDispatcher
which should report platform-level errors so maybe that's why Stacktrace.current
doesn't make much sense.
You could also send your event link to giancarlo.buenaflor@sentry.io (this is my email) so I can take a closer look
I nailed it down to https://github.com/dart-lang/sdk/issues/56431
Closing this as it'll be fixed by https://dart-review.googlesource.com/c/sdk/+/380982
Platform
Flutter Mobile
Obfuscation
Disabled
Debug Info
Disabled
Doctor
Version
8.6.0
Steps to Reproduce
Sentry is configured to capture exceptions. This is the issue and a complete stack trace I'm getting from the Sentry's error handler, which has next to nothing info about the actual error.
Expected Result
The reported stack trace should have enough info about the actual issues.
Actual Result
The reported stacktrace is not relevant to the app's issue and has references to Sentry's own code.
Are you willing to submit a PR?
None