Jonas Uekötter

Example: https://sentry.io/organizations/sentry-sdks/issues/2613488099/?project=5428562

> looks like the macOS hang again https://github.com/getsentry/sentry-dart/pull/576/checks?check_run_id=3472320682 Ahhh, I really dislike that error :(

The only way I see to archive this currently is to advise the user to include the pubspec.yaml file as an asset and read the dart and flutter version constraints...

Dart issue for exposing more information at runtime: https://github.com/dart-lang/sdk/issues/46347

Are there any updates on this?

In the meantime, would it be possible to add a tag like `uncaught = true` for each exception which isn't handled but also doesn't crash the app? I do understand...

Crashlytics also records [unhandled exceptions in Flutter as fatal](https://firebase.google.com/docs/crashlytics/get-started?platform=flutter#configure-crash-handlers) which is kinda the same as the unhandeld in Sentry.

I think so. That would make it possible to do ```dart Sentry.captureException( exception, withScope: (scope) { scope.addAttachment(ScreenshotAttachment()); }, ); ```

Here's the list: ``` device.language device.timezone device.screenResolution device.theme ``` Speaking of removing deprecated fields, there are a couple more candidates: - https://github.com/getsentry/sentry-dart/blob/6ae0ef03535461e6a75d1eb297e71376eaeed749/dart/lib/src/enricher/io_enricher_event_processor.dart#L95-L96 since it was moved to `event.thread.name` and can...

https://github.com/getsentry/sentry-dart/pull/934 introduced attaching http response data, so the MaxRequestBodySize and MaxResponseBodySize enums can be consolidated.