Jonas Uekötter

Add how much space an app takes up on the user's device

16

### Problem Statement In the iOS settings (General -> Storage) I can see how much space an app takes up. This is split into: - App Size - Documents &...

Notifiy user of invalid trace rate setting

1

Performance tracing doesn't work if both the tracesSampler and the traceSampler rate is set. There should be some sort of error when the user does it. This enlightenment come out...

The idea is to detect shader compilation jank and then tell users, that they can improve it by following https://docs.flutter.dev/perf/shader. Shader compilation only happens on a cold app start. Which...

Performance tracing should use Timeline

1

The Dart Dev tools include a performance view similar to the one of Sentry, see - https://dart.dev/tools/dart-devtools - https://docs.flutter.dev/development/tools/devtools/performance - https://docs.flutter.dev/development/tools/devtools/cpu-profiler If Sentry adds Timeline events (see [Timeline](https://api.dart.dev/stable/2.17.6/dart-developer/Timeline-class.html) and [TimelineTask](https://api.dart.dev/stable/2.17.6/dart-developer/TimelineTask-class.html))...

See https://github.com/invertase/github-action-dart-analyzer It can be used for all projects in this repository.

Remove deprecated device context fields

3

There are a couple of fields which are deprecated in the device context. Those fields should be removed in v7.0. Follow up from #838

sentry_dio has currently no version test. Ideally, this should be added. See https://github.com/getsentry/sentry-dart/pull/914#discussion_r912664032 Version test is something like this https://github.com/getsentry/sentry-dart/blob/d75a8c698a4942816336f3bae9a50c87fa6be0a8/dart/test/version_test.dart#L1-L21

Exceptions not handled by user code should be `unhandled: true`

11

Currently all exceptions are marked as `handled`. This decision was made because exceptions in Flutter don't crash the app and thus sessions should not be marked as crashed. Though we...

`attachThreads` should attach native threads even if the exception comes from Dart/Flutter

1

If I enable the `attachThreads` option, I would expect that native threads are attached to my crash-reports, even if the crash reports come out of the Dart/Flutter layer. One tricky...

One can detect wether Flutter for Web runs with the HTML renderer or the CanvasKit renderer like this: ```dart import 'dart:js' as js; final dynamic flutterCanvasKit = js.context['flutterCanvasKit']; if(flutterCanvasKit !=...