Manoel Aranda Neto

Let's wait for this before doing the FE changes (hiding Sentry frames) and adding the detector for Dart/Flutter SDK as well.

> > SentryStackFrame#absPath cus we strip the path to the last segment due to PII. > > Just wanted to say paths to source files/debug files aren't considered PII in...

Ps: Right now the `absPath` is the very same as `fileName` which is just the last segment of the `Frame.uri`, for example: `dart:ui/hooks.dart` becomes `hooks.dart`, I've changed to the full...

Seems like supporting Source code context for apps not using `split-debug-info` would require quite a bit of work, probably making our own version of `source bundle` or loading source code...

FE already does something similar with the `absPath` -> package heuristics https://github.com/getsentry/sentry/blob/0260a8769124adad82ada598ed960b36468bf233/src/sentry/utils/event_frames.py#L59-L79 This is for [Stack Trace Linking](https://docs.sentry.io/product/integrations/source-code-mgmt/github/) IIRC.

Flutter is investing in [multiple windows support](https://medium.com/flutter/flutter-in-2023-strategy-and-roadmap-60efc8d8b0c7) this year, so this will likely be a problem soon.

Lets consider doing a study group for this because other SDKs would have the same problem, multiple windows for Android, iOS and most likely others as well, the problem lives...

We have to discuss the meta issue and define the scope beforehand.

Yes, but it depends on Android and iOS first.

https://github.com/DiederikvandenB/apollo-link-sentry also uses the Link approach for RN, so using the Link approach would be the way to go.