Skip to content

Need a plan for reporting Dart crashes #614

Description

@eseidelGoogle

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

Activity

  1. added
    c: new featureNothing broken; request for a new capability
    frameworkflutter/packages/flutter repository. See also f: labels.
    engineflutter/engine related. See also e: labels.
    on Dec 11, 2015
  2. added this to the milestone on Dec 11, 2015
  3. Hixie commented on Dec 11, 2015

    @Hixie
    Contributor

    We also need engine crash reporting.

  4. sethladd commented on May 20, 2016

    @sethladd
    Contributor

    Firebase now has crash reporting: https://firebase.google.com/docs/crash/

  5. eseidelGoogle commented on May 31, 2016

    @eseidelGoogle
    ContributorAuthor

    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

  6. sethladd commented on Nov 30, 2016

    @sethladd
    Contributor

    See also this related Gallery link: flutter-team-archive/gallery#633

  7. modified the milestones: , on Jan 26, 2017
  8. 11 remaining items

  9. sethladd commented on Jun 13, 2017

    @sethladd
    Contributor

    We found our contacts in Crashlytics and we have a meeting scheduled for Wednesday. Hope to kick if off real soon!

  10. self-assigned this
    on Jun 14, 2017
  11. sethladd commented on Jun 15, 2017

    @sethladd
    Contributor

    Should we de-dupe with #9592 ?

  12. yjbanov commented on Jun 15, 2017

    @yjbanov
    Contributor

    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.

  13. Hixie commented on Jun 27, 2017

    @Hixie
    Contributor

    @yjbanov What more needs to happen for you to consider this bug closed?

  14. yjbanov commented on Jun 27, 2017

    @yjbanov
    Contributor

    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.

  15. magick93 commented on Aug 12, 2018

    @magick93

    I 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?

  16. yjbanov commented on Aug 13, 2018

    @yjbanov
    Contributor

    @magick93 this issue is about ability to report crashes in general. The Crashlytics issue is tracked here: #14765.

  17. github-actions commented on Sep 2, 2021

    @github-actions

    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 -v and a minimal reproduction of the issue.

  18. locked as resolved and limited conversation to collaborators on Sep 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

c: new featureNothing broken; request for a new capabilitycustomer: posse (eap)engineflutter/engine related. See also e: labels.frameworkflutter/packages/flutter repository. See also f: labels.

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions