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
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.
@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.
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
Reacted by Kristiyan Mitev, Ahmed Tarek, Ben Hagen, Antti Ahti, Cayke Prudente, Anisov Aleksey, Per Lycke, Karen, Jesper We, Pujit Mehrotra and 3 more
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.
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.
Reacted by Antti Ahti, Karen, Gregory Sech and DazzaH0
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
Reacted by Jerry Chen, Karen, Gregory Sech, Pujit Mehrotra, Maksim Lin, Vegard Stene, Matheus and Amr Abd-Alkrim
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
jaumard commentedon 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 commentedon 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 commentedon Mar 20, 2019
Sure no problem @kroikie :) just wanted to be sure it was still the plan ^^
Thanks !
audkar commentedon 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:
shhh9 commentedon 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 commentedon 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 commentedon 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 commentedon Oct 2, 2019
Any news on this?
kroikie commentedon Oct 13, 2019
@kroikie
This issue has been moved to firebase/flutterfire#398. Any further collaboration will be done there.
github-actions commentedon Aug 27, 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.