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
{{ message }}
Repository navigation
[firebase_crashlytics] Please add Crashlytics fatal crash support #398
This should be a high priority. In order to release production apps we should have fatal crash reports. Any progress on this?
Reacted by Natan Lotério, Yamauchi, Turki Alhazzani, Luka Knezić, Koen Van Looveren, Aleksandr Yurkovskiy, Iurii Dorofeev, dwayne-roadhouse, Ludwik Trammer and Victor
The way it is now, flutter errors are being mixed with other type of issues since we have also native code on our app. Having support for crashes will let us have more visibility of flutter code problems.
Reacted by Mark Kessler, Julia Vi, Iurii Dorofeev and Reinaldo Moreira
Could we please get an ETA here? It is a bit tough to monitor a release using just non-fatal errors. This prevents us from getting an accurate number for "crash-free users" as well. Also, no spikes are reported for non-fatal errors so all monitoring needs to be done manually. 😞
Activity
kroikie commentedon Oct 13, 2019
@kroikie
The issue at flutter/flutter#29689 has been closed and moved here. Future collaboration on this issue will be done here.
vanlooverenkoen commentedon Nov 6, 2019
This should be a high priority. In order to release production apps we should have fatal crash reports. Any progress on this?
kroikie commentedon Nov 9, 2019
@vanlooverenkoen this is high priority for us; and we are working on it. I will leave this issue open for tracking progress.
talhazzani commentedon Dec 23, 2019
We're counting on you @kroikie
vanlooverenkoen commentedon Jan 20, 2020
Any update on this?
sanekyy commentedon Feb 2, 2020
Hi there.
I see fatal crashes in Firebase Console, but logs are missed.
In non-fatal crashes logs are present.
Here is example of fatal crash. Only analytics events are present.
Is it related issue?
[-]Please add Crashlytics fatal crash support[/-][+][firebase_crashlytics] Please add Crashlytics fatal crash support[/+]dccruzt commentedon May 11, 2020
Any update on this?
The way it is now, flutter errors are being mixed with other type of issues since we have also native code on our app. Having support for crashes will let us have more visibility of flutter code problems.
otopba commentedon Jul 7, 2020
I have same problems =/
Truba commentedon Nov 25, 2020
Any update on this?
I'm sorry, I know I'm just repeating the question, but I really don't want this issue to get killed due to inactivity 😊
vanlooverenkoen commentedon Nov 25, 2020
@kroikie is this still a high priority? We are 1 year later. And this is still not supported?
dotdoom commentedon Nov 25, 2020
2.5 years, in fact flutter/flutter#14765 :-)
rohan20 commentedon Mar 3, 2021
Could we please get an ETA here? It is a bit tough to monitor a release using just non-fatal errors. This prevents us from getting an accurate number for "crash-free users" as well. Also, no spikes are reported for non-fatal errors so all monitoring needs to be done manually. 😞
Salakar commentedon Mar 22, 2021
👋 hey all, we're currently in the process of adding a way to report a Dart error as fatal from Dart code. PR coming soon.