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
Sentry Flutter Android does not capture any exceptions at all when custom initialization - caused by callback failure, thus would be great to add a log / throw when this happens #1486
Comments
I see the problem:
if enabling the So, now the issue becomes: It would be great to have a more user friendly hint when there are errors. For example, when such initialization fails, we may either:
Anyway this is just a tiny suggestion. But hopefully this can save developers' time in the future. Because the bug is not that trivial to recognize currently, while adding a log or a throw will make it quite trivial to fix. |
@fzyzcjy thanks for the feedback. For
https://docs.sentry.io/platforms/android/enriching-events/breadcrumbs/ Now to the issue:
|
^ by doing #1489 If the |
Thanks but I hope other integrations are enabled (only disable temp sensor - otherwise some app stores are unhappy)
|
Platform
Flutter Mobile
Obfuscation
Disabled
Debug Info
Disabled
Doctor
latest
Version
latest
Steps to Reproduce
Custom initialization:
And disable Dart side auto initiailization:
Then,
Sentry.captureException(...)
.Extra experiment and possible cause analysis
I have compared two cases:
I see both cases call
SentryClient._attachClientReportsAndSend
andFileSystemTransport.send
happily. Indeed, with the following extra logs, I can see "hi 1" and "hi 2" both.I will update my findings here. If I can fix it, hopefully this issue can be used as a future reference for who wants to manually initialize sentry.
Expected Result
See exception sent to sentry server
Actual Result
No exception sent to sentry server
Are you willing to submit a PR?
None
The text was updated successfully, but these errors were encountered: