Please add support for Crashlytics

[dotdoom]

In #9592 there's a request for adding Crashlytics, but it was blocked by an absence of crash reporting support in Flutter. Now that there are ways to intercept errors, it should be possible to add Crashlytics / Firebase error reporting.

[xster]

cc @collinjackson might have updates.

I'd like to use it for the gallery as well flutter/gallery#633

[hocinehamdi]

It will be perfect to have first class dart crash reporting tool

[pulyaevskiy]

Very much interested in this as well. It would be great to have crash reports in Firebase console for both Dart and native side errors.

[PareshMayani]

Indeed it's much needed thing! Looking forward for either crashlytics or Firebase integration

[ekbiker]

This would be awesome.

[wahibhaq]

I had to use Crashlytics and ended up on this page. It would be really nice to have it for flutter 🙏

[jpgilchrist]

Given the latest updates in Google I/O, this seems like a pretty obvious thing to include. firebase_analytics plugin already provides the google analytics portion. However, the crashlytics isn't available, which is a major part of the firebase offerings.

[rodydavis]

Definitely would love this plugin!

[eseidelGoogle]

Looks like this is now our top most requested issue. :D

@yjbanov looked at this briefly last year and determined it would require some changes to Crashlytics itself to add Dart support. We'll reach out to the crashlytics team again and see how things have changed in the intervening months. This seems like a very reasonable request and should definitely be doable. Just a question of when. :)

[eseidelGoogle]

I spoke with @collinjackson a while back and it sounded like they or @kroikie or @bparrishMines were interested in taking this on. I believe mostly this requires some coordination with the crashlytics team. FWIW this is still our top-most requested bug. :)

[ChristBKK]

+1 for this one

[gonzalonm]

Any news on this? I would really appreciate to have Crashlytics integration on Flutter!

[vithanichandresh]

+1

[jjbeto]

+1

[jaumard]

Any news on this ? Did the plugin start ? I want to take a look see if I can help. Would be nice to use Crashlytics (and other reporting tool of Fabric) with Flutter as we're using a lot of functionality of Fabric into our native app already.

[karantanwar]

it would be great to have this plugin

[jaumard]

Hello everyone, I've just implemented a plugin for Crashlytics integration for iOS and Android. Reports look like this:

It's not perfect but at least it's a start :) it can also allow you to set custom logs and informations (general and user info) from Dart.

Let me know what you think of it guys.

One limitation is that as the report is with Crashlytics SDK, it reports manual exceptions as Non Fatal, one way to bypass that would be to make the app crash, I've opened an issue on my repo to collect thoughts about this.

Here is the repo https://github.com/kiwi-bop/flutter_crashlytics and the pub packages https://pub.dartlang.org/packages/flutter_crashlytics

[nstrelow]

It would be awesome to get official support for Crashlytics!

[neiljaywarner]

@Hixie @eseidelGoogle @kroikie Can we please get a recipe on flutter.io that does not require a sentry.io account?

Ideally with a link to a section somehow detailing pros and cons compared to the first-class support that is a work in progress.

It looks like crashlytics support is "good enough" right now but improving, but i can't figure out yet how to clarify that, and the need is increasing. thank you

[Hixie]

@neiljaywarner are you asking for sample code that doesn't involve sentry.io?

[neiljaywarner]

Yes please
The path of least friction to crashlytics as of feb2019 would help a lot of people I think

[hummatli]

I like the idea! Google must do this!

[GreenAppers]

Debugging my app's SIGSEGV in libflutter.so, I've been working to extend flutter_crashlytics to include CrashlyticsNdk and thereby actually catch SIGSEGV and report it.

However I have not been able to successfully symbolicate the crashes.

The problem seems to be that "flutter build" produces no artifacts with debugging symbols. The files under build/app/intermediates/transforms/stripDebugSymbol and build/app/intermediates/transforms/mergeJniLibs are nearly same size, and it seems that none of them contain debugging symbols.

We need to modify "flutter build" to produce some libflutter.so with debugging symbols. Then configure build.gradle like:

crashlytics {
enableNdk true
androidNdkOut "../../build/app/intermediates/transforms/mergeJniLibs/release/0/lib"
androidNdkLibsOut "../../build/app/intermediates/transforms/stripDebugSymbol/release/0/lib"
}

And upload with ./gradlew crashlyticsUploadSymbolsRelease.

Many, if not all, flutter_crashlytics users need this. As I've learned, writing a pure Dart app will not protect you from native crashes. Without CrashlyticsNdk we can't learn of users' SIGSEGV, and without changes to "flutter build" we can't symbolicate them.

[eseidelGoogle]

https://github.com/flutter/flutter/wiki/Crashes includes instructions on how to get flutter.jar and flutter.framework files with symbols in them. Let me know if that doesn't help?

[GreenAppers]

Thanks for this and the quick response. This is exactly what I needed.

It would be nice to find an easier solution to getting these uploaded to Crashlytics.

[GreenAppers]

I would appreciate any comments on PR towards symbolicating native crashes in Flutter apps with Crashlytics: https://github.com/kiwi-bop/flutter_crashlytics/pull/64/files

Before:

After:

Until I can fix the bug I don't know if these frames are correct. They seem plausible because this crash is preceded by video artifacts in canvas.

[MisterJimson]

Should this be closed? The pub link on the readme goes nowhere. Is the package published?

https://github.com/flutter/plugins/tree/master/packages/firebase_crashlytics

[jaumard]

Also notice that is a partial support, as it does not more than flutter_crashlytics and have same limitations... the main who is that crash are reported as non fatal :/

[kroikie]

@MisterJimson The pub link should be working now.

@jaumard You are correct that the crashes are reported as non fatal. Future versions will address this, thanks for the feedback.

[kroikie]

Filed an issue for fatal support

[kroikie]

@dotdoom

This issue has been moved to firebase/flutterfire#903. Any further collaboration will be done there.

[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.