Have I finally gone blind or is there not an obvious way to delete Firebase Crash reports through the Google Firebase web console? My Android app is successfully logging reports but now I have a flood of "development crashes" that are eating up a lot of my view in the console. It makes it very difficult to find actual beta user crashes (especially since I also can't seem to filter the crashes by date/time). Any help is much appreciated.
If you want to disable data collection by default for all app runs, add the firebase_crashlytics_collection_enabled flag to your app's AndroidManifest.
Go to the Crashlytics dashboard of the Firebase console to see your test crash.
Firebase Crashlytics is a lightweight, realtime crash reporter that helps you track, prioritize, and fix stability issues that erode your app quality. Crashlytics saves you troubleshooting time by intelligently grouping crashes and highlighting the circumstances that lead up to them.
To mark a cluster as closed, click the three dots on the far right of the row that appear when hovering over the row, then click "close cluster."
The best thing you can do for the long term is to create two different instances of the app, one for debug/dev and another for release, and make sure they have different package names. This should allow you to view them each independently in the console. You can configure this pretty easily in your build.gradle.
This topic was also discussed in more detail on our firebase-talk group, but from the perspective of Firebase Analytics. Be sure to click through to get more details on how the gradle build works.
As far as actually deleting the issues that come up, there's not currently a way to do that, but we are looking into that for a future release. We definitely hear everyone's feedback on that.
I know this is old, but now there is a way to disable Crashlytics
when in debug mode.
In your app level build.gradle
:
apply plugin: 'com.android.application'
apply plugin: 'io.fabric'
android {
//...
buildTypes {
release {
minifyEnabled true
shrinkResources true
proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
manifestPlaceholders = [crashlyticsEnabled: true]
}
debug {
manifestPlaceholders = [crashlyticsEnabled: false]
}
}
}
//...
And in your AndroidManifest.xml
inside application
tag:
<meta-data
android:name="firebase_crashlytics_collection_enabled"
android:value="${crashlyticsEnabled}" />
It has the option to Close the issue in the GUI. I have attached the screenshot for reference..
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With