FabricPlugin icon indicating copy to clipboard operation
FabricPlugin copied to clipboard

Is it possible to force Fabric to stop sending crash report temporary?

Open hung-doan opened this issue 8 years ago • 3 comments

I'm finding an option to disabled Fabric temporary - to make sure It doesn't send any thing to Fabric in development/testing mode.

And Fabric will be enabled again in distribution mode.

hung-doan avatar May 11 '16 08:05 hung-doan

No, there is no way to temporarily disable the plugin. You can, however, use one of the two solutions below to differentiate your dev builds from your production builds.

Option 1: Set a key/value pair that indicates if it is a development build. These key/value pairs show up in the crash details for each crash entry.

window.fabric.Crashlytics.setBoolValueForKey(true, "isDevelopmentBuild");

Option 2: Use a different package ID for your development builds. For example, com.company.yourapp for production builds and com.company.yourapp.dev for development builds. Fabric will treat the package ID as a different app and completely seperate all crashes and answers events in the Fabric console.

Justin-Credible avatar May 11 '16 16:05 Justin-Credible

@Justin-Credible Thanks you for your suggestions. I think I will stick with "Option 2" as an temporary solution.

About this feature. I found this document for android: https://docs.fabric.io/android/crashlytics/build-tools.html I wonder if we can implement this feature!. According to the document, There are 2 options to disabled Fabric:

  • At build time : We can implement a build hooks to update build configuration
  • At run time: Or disabled fabric at run-time.

hung-doan avatar May 12 '16 04:05 hung-doan

It would be nice if we could disable Fabric on dev builds though, we just don't want to clutter our crash reporting stats.

losbeekos avatar May 18 '18 10:05 losbeekos