Repository navigation
Need a plan for reporting Dart crashes #614
Description
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?
Activity
Hixie commentedon Dec 11, 2015
We also need engine crash reporting.
sethladd commentedon May 20, 2016
Firebase now has crash reporting: https://firebase.google.com/docs/crash/
eseidelGoogle commentedon May 31, 2016
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
sethladd commentedon Nov 30, 2016
See also this related Gallery link: flutter-team-archive/gallery#633
11 remaining items
sethladd commentedon Jun 13, 2017
We found our contacts in Crashlytics and we have a meeting scheduled for Wednesday. Hope to kick if off real soon!
sethladd commentedon Jun 15, 2017
Should we de-dupe with #9592 ?
yjbanov commentedon Jun 15, 2017
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.
Hixie commentedon Jun 27, 2017
@yjbanov What more needs to happen for you to consider this bug closed?
yjbanov commentedon Jun 27, 2017
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.
magick93 commentedon Aug 12, 2018
Where do I find information about the Crashlytics Flutter solution?
yjbanov commentedon Aug 13, 2018
@magick93 this issue is about ability to report crashes in general. The Crashlytics issue is tracked here: #14765.
github-actions commentedon Sep 2, 2021
This 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.