You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for opening #14765 -- for anyone interested in Crashlytics support, please cast a vote by pressing thumbs-up on the top-most comment in that new bug.
Reacted by Paresh Mayani, Florian Gabach, Tudor Luca, Ivan Lugo, Edouard Marquez, andaas4, Guilherme Souza, francorolando, Dirk Steinkopf, Ted Liao and 87 more
on September 9th, 2018, Firebase Crash Reporting will be fully retired and you will no longer have access to that part of the console.
Since firebase crash reporting just announced they are retiring it in firebase in 60 days do we have an update for when crashlytics will be available for flutter?
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.
Activity
sethladd commentedon Apr 25, 2017
See also #614 and flutter-team-archive/gallery#633
sethladd commentedon Apr 25, 2017
FWIW, another potential strategic partner has asked for Crashlytics.
FaisalAbid commentedon Apr 25, 2017
Is it currently possible right now to capture the stack trace when something crashes?
eseidelGoogle commentedon Apr 25, 2017
It's possible to capture a dart stack trace: #614 (comment)
FaisalAbid commentedon Apr 25, 2017
Thanks thats helpful.
I wonder how Crashlytics/Firebase Crash reporiting will handle non ObjC/Java stack traces assuming they allow custom crash uploads.
We need this for Tunes app also, i'll experiment and report back
FaisalAbid commentedon Apr 27, 2017
Possible with FirebaseCrashReports if you do the following
Wrap up the crash from flutter in an Android Exception
FirebaseCrash.report(new Exception(flutterCrashString));And that will be reported in the console
lukef commentedon Jun 1, 2017
Google is recommending to NOT use firebase for crash reporting on new projects anymore. I would suggest we close this issue.
eseidelGoogle commentedon Jun 1, 2017
https://firebase.google.com/docs/crash/
eseidelGoogle commentedon Jun 1, 2017
Actually, I think we can keep this open, it's just about providing crashlytics integration.
4 remaining items
eseidelGoogle commentedon Jun 15, 2017
I believe @yjbanov is actively working on this.
[-]Would like a crash reporting plugin[/-][+]Would like a Crashlytics plugin[/+]yjbanov commentedon Jun 29, 2017
Unassigned for now because I'm not actively working on it. Still on the roadmap though.
sethladd commentedon Nov 15, 2017
A crash reporting option is here: https://pub.dartlang.org/packages/sentry
Hixie commentedon Dec 18, 2017
Closing as dupe of #614.
dotdoom commentedon Feb 9, 2018
Looks like #614 was closed without implementing Crashlytics support.
Moreover, it was suggested to make incremental enhancements.
@Hixie Do you think it's reasonable to reopen this now as an incremental enhancement to crash reporting?
Hixie commentedon Feb 13, 2018
Please don't hesitate to open a new bug. Probably best not to re-use this one since it has a confusing history and not much useful information.
mit-mit commentedon Mar 2, 2018
Thanks for opening #14765 -- for anyone interested in Crashlytics support, please cast a vote by pressing thumbs-up on the top-most comment in that new bug.
rodydavis commentedon Jul 12, 2018
Since firebase crash reporting just announced they are retiring it in firebase in 60 days do we have an update for when crashlytics will be available for flutter?
nokia6290 commentedon Sep 4, 2018
@AppleEducate I believe it means crashlytics will be default crash analytics for firebase Analytics.
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.