Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please add Crashlytics fatal crash support #29689

Closed
kroikie opened this issue Mar 20, 2019 · 9 comments
Closed

Please add Crashlytics fatal crash support #29689

kroikie opened this issue Mar 20, 2019 · 9 comments

Comments

@kroikie
Copy link

@kroikie kroikie commented Mar 20, 2019

Currently the Crashlytics plugin is limited to only report non-fatal reports. It would be nice to have the ability to report fatal reports as well.

@jaumard

This comment has been minimized.

Copy link
Contributor

@jaumard jaumard commented Mar 20, 2019

The issue here is that the native crashlytics libraries doesn't let you specify if the crash is fatal or not, so all the one you report manually are tagged as non fatal. Would be nice if the crashlytics libraries allows us to specify this. I understand that it will need synchronization with the crashlytics team to do that, but that was the point of #14765 to do it :)
So here I'm not sure it's the same feature as the one you describe as normally the ability to report fatal reports (meaning native crashes) should already be available on the PR you did.

@kroikie

This comment has been minimized.

Copy link
Author

@kroikie kroikie commented Mar 20, 2019

@jaumard the idea was to provide official support for Crashlytics. We are working on fatal reporting integration which as you mentioned requires work with the Crashlytics team but we did not want that work to totally block the publishing of an official plugin.

@jaumard

This comment has been minimized.

Copy link
Contributor

@jaumard jaumard commented Mar 20, 2019

Sure no problem @kroikie :) just wanted to be sure it was still the plan ^^
Thanks !

@audkar

This comment has been minimized.

Copy link

@audkar audkar commented Jul 25, 2019

Can you make a friendly ping to Firebase team from time to time regarding this issue? These are actual hard limitations for productions apps. No serious company will release product on platform where no crash reporting tool available which:

  • Reports issues as they happen (limitation of non-fatal issues on Firebase)
  • Has capability to deobfuscate crash reports.
  • Lets to Opt-out
@shhh9

This comment has been minimized.

Copy link

@shhh9 shhh9 commented Aug 12, 2019

Exactly as @audkar said. In order for Flutter to be production-ready, all these basic logging and reporting requests should be of high priority to the team. Proving production-grade features is the best way to drive up Flutter adoption and show its potential.

@audkar

This comment has been minimized.

Copy link

@audkar audkar commented Aug 12, 2019

Working crash reporting service was most requested ticket on Flutter repository. It was closed as solved... which is obviously not the case. Real projects requires service which correctly tracks issues in app. There is none for Flutter and community can't do much here.
@eseidelGoogle mentioned in comment that flutter team started talking about this issue with Firebase team two years ago, but seems no progress was made since then.
This is so bad and sad that any crash tracking service has real support for Flutter.

@eseidelGoogle

This comment has been minimized.

Copy link
Contributor

@eseidelGoogle eseidelGoogle commented Aug 12, 2019

I've reached out to the team again last week, they had a lot on their plates last time we talked. You're also welcome to submit a direct request via the various Crashlytics/firebase support channels. I'm sorry I don't have a better answer at this time, but I'll keep asking. FYI @csells @shobhitchugh

@froesmatheus

This comment has been minimized.

Copy link

@froesmatheus froesmatheus commented Oct 2, 2019

Any news on this?

@kroikie

This comment has been minimized.

Copy link
Author

@kroikie kroikie commented Oct 13, 2019

@kroikie

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

@kroikie kroikie closed this Oct 13, 2019
@kroikie kroikie added the transferred label Oct 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
8 participants
You can’t perform that action at this time.