When Sentry-Android handles a runtime exception with its uncaughtExceptionHandler it doesn't appear to add any accumulated breadcrumbs to the event posted to the Sentry server, whereas manually caught exceptions posted with Sentry.captureException and Sentry.captureEvent do include breadcrumbs.

Is there a reason why the uncaughtExceptionHandler omits breadcrumbs? It would be quite useful for determining the events leading up to a runtime crash.

Would it be possible to add this for uncaught exceptions in a future release?

I'm currently using Sentry-Android 1.5.2 in my app as this appears to be the latest I can get from jCenter.