Jonas Uekötter

Yes, this actually does improve performance by not introducing an asynchronous gap. > For consistency and smaller code, an await e where e evaluated to a non-future would wrap that...

> Breadcrumbs and spans for fetch/xmlhttprequest This should not create duplicates when used together with the `http` or `dio` integrations.

Even if it's not awaited it's still running on the UI isolate.

Thanks for raising the issue. This is already fixed in https://github.com/getsentry/sentry-dart/pull/533 I think it's already in the latest beta but it will be available in the next version.

Error are shown in the debug console (e.g. VS Code or IntelliJ). As far as I know they aren't shown in the browser which is the connected device. You probably...

Ah I see, yeah that looks like an bug. We'll check it out.

Do we want an E2E Test for each platform? I imagine that web and desktop could be easier than mobile because we don't need an emulator/simulator.

Current status: - [x] Dart application - [ ] Flutter Web - [ ] Flutter Mobile - [ ] Flutter Desktop

It is an older event of the same exception https://sentry.io/organizations/sentry-sdks/issues/2149575550/events/0fb9c693eea84858b8b0a6986a7e16e6/?project=5428562

Yeah, that time span seems reasonable