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.
相关问题
- How can I create this custom Bottom Navigation on
- Bottom Navigation View gets Shrink Down
- How to make that the snackbar action button be sho
- Listening to outgoing sms not working android
- How to create Circular view on android wear?
相关文章
- android开发 怎么把图片放入drawable的文件夹下
- android上如何获取/storage/emulated/下的文件列表
- androidStudio有个箭头不认识
- SQLite不能创建表
- Windows - Android SDK manager not listing any plat
- Animate Recycler View grid when number of columns
- Why is the app closing suddenly without showing an
- Android OverlayItem.setMarker(): Change the marker
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.
As Doug answered, it isn't possible at the moment.
My method is to use the filter - when in dev/debug, you roll the version forward one minor version, and when you release you, use another version.
This way you can restrict errors that you're dealing with to your current version, and not changing the package names, or having two code branches open.
I know this is old, but now there is a way to disable
Crashlytics
when in debug mode.In your app level
build.gradle
:And in your
AndroidManifest.xml
insideapplication
tag: