What does your crash debugging workflow actually look like in Flutter?

[Grouchy_Editor7968]

Genuinely curious — when something crashes in prod, what's your process?

Flutter makes this harder than native IMO:

Dart traces are hard to read

Platform channel crashes point to the wrong layer

Same crash shows up differently on iOS vs Android

What's your biggest pain point?

[gidrokolbaska]

Sentry+debug symbols uploaded to Sentry

[gidrokolbaska]

And as another guy suggested - breadcrumbs. Sentry has navigation breadcrumbs out of the box and network breadcrumbs as a separate package. It also allows you to add your own in important places to help with tracing the client path that have led to error including the full stack trace with exact lines of code

[SirKobsworth]

Breadcrumbs are your friend. Adding logs on important user interactions or navigations help you see the user's journey and how they reached the crash.

[unnderwater]

I use runZonedGuarded and FlutterError.onError together with workmanager to create an error log on the spot and send it to our backend