Menu
Recently, I decided to migrate from Parse and use the lighter and easier tool, Crashlytics. I've been playing with the interface for a long time and it is already responding every developer needs except one thing:
In addition to close an issue, Is it possible to permanently remove a crash from the crash list in dashboard?
In my case, I planted some force crashes (by throwing a simple RuntimeException) in order to test the performance and stability of Crashlytics, but now seeing them beside real crashes is completely on my nerve. Any idea on how to get rid of them?
258
Here's a couple of ways to disable Crashlytics while you are doing your debug builds! Use a different android:versionString for debug and release builds and then disable crash reporting from the Crashlytics web dashboard for the debug version. Wrap the call to Crashlytics.
Crashlytics helps collecting, analyzing and organizing app crash reports.
In addition to automatically reporting your app's crashes, Crashlytics lets you record non-fatal exceptions and sends them to you the next time your app launches. Note: Crashlytics only stores the most recent eight exceptions in a given app session.
You can't completely remove the crashes. You can, however, only show crashes that are open instead of showing all crashes as it sounds like you might be doing. You could also increment your app version, but that may not be of that much use to just hide crashes that you forced for testing.
98
You can close the issue, so it will not be shown again for the reported version.
37
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
