Repository navigation
Need a plan for reporting Dart crashes #614
Description
Activity
- addedc: new featureNothing broken; request for a new capabilityNothing broken; request for a new capabilityframeworkflutter/packages/flutter repository. See also f: labels.flutter/packages/flutter repository. See also f: labels.engineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.
on Dec 11, 2015 We also need engine crash reporting.
Firebase now has crash reporting: https://firebase.google.com/docs/crash/
Now that we use AOT dart in release mode, this plan is likely the same as flutter-team-archive/gallery#633, but we will also need to be sure we can explain to devs how to symbolicate AOT dart stack traces? FYI @zanderso
See also this related Gallery link: flutter-team-archive/gallery#633
- modified the milestones: This milestone has been deleted, This milestone has been deleted
on Jan 26, 2017 11 remaining items
We found our contacts in Crashlytics and we have a meeting scheduled for Wednesday. Hope to kick if off real soon!
Reacted by Óscar Caballero, Patrick Boos, satya1395 and Purusothaman RamanujamShould we de-dupe with #9592 ?
It's probably going to be hard to cover a complete crash reporting solution with one issue. That said, breaking down the tasks into issues requires some system, so I'm OK with deduping, and if we care to capture sufficient aspects of crash reporting, we could start a GitHub project and log multiple issues there.
@yjbanov What more needs to happen for you to consider this bug closed?
I think we have an 80% solution, so I'm OK with closing and switching to an incremental enhancements mode.
For users who would like to start collecting crash reports from their app now, check out package:sentry.
Reacted by Günter Zöchbauer, Łukasz Byjoś and Lorenzo PieriI think we have an 80% solution, so I'm OK with closing and switching to an incremental enhancements mode.
Where do I find information about the Crashlytics Flutter solution?
Reacted by Neil Jay WarnerThis thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.- locked as resolved and limited conversation to collaborators
on Sep 2, 2021
Presumably we could integrate with existing Android Crash reporting:
https://developers.google.com/analytics/devguides/collection/android/v4/exceptions
Unclear what a solution is on iOS?
@johnmccutchan @Hixie