Jonas Uekötter

Image the following scenario: - I'm using package `dio` with package `graphql` - The http request fails for whatever reason The `graphql` package now catches the `DioError` from the `dio`...

I would like to have an API which is like `Sentry.captureException` but without the sending it to Sentry. That way, it's easy to recursively create events and merge them in...

I've played around a bit and came up with this proof-of-concept: ```dart import '../sentry.dart'; import 'utils/isolate_utils.dart'; class NestedExceptionUtil { Future eventFromException({ required SentryOptions options, required Object exception, StackTrace? stackTrace, })...

That's actually a very good question. I'm guessing it's just about the `isWeb` check for now. But when WASM for Dart/Flutter eventually gets rolled out, it should definitely be tested.

I don't really think this is a framework bug. For example ```Dart SingleChildScrollView( scrollDirection: Axis.horizontal, controller: horizontalScrollController, child: SingleChildScrollView( scrollDirection: Axis.vertical, controller: verticalScrollController, child: child, // must be big enough...

Closing in favor of https://github.com/getsentry/sentry-dart/pull/1088

This doesn't seem to be fixed, since the overridden `onError` doesn't call `presentError`, as seen in: https://github.com/getsentry/sentry-dart/blob/a60913453866bc81901784aec6fa8aad023135f8/flutter/lib/src/integrations/flutter_error_integration.dart#L22-L98 The default implementation for `onError` does it, though: `static FlutterExceptionHandler? onError = presentError;`...

Hey, would you be willing to contribute this as a PR?

Hey, are you open to fixing it and contributing it via PR?

You can actually do this via a custom feedback builder.