Android的禁用Crashlytics在图书馆项目进行调试 [英] Android Disable Crashlytics In Library Project For Debug

查看:174
本文介绍了Android的禁用Crashlytics在图书馆项目进行调试的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有多个模块的项目。模块的共同code是一个库模块中。问题是,我们最近增加了Crashlytics到我们的项目(库模块中),我们不断收到错误报告,即使我们处于调试模式。我在互联网上搜索,我发现了一个库总是被视为一种释放模式。现在的问题是,有没有办法在我的情况禁用​​Crashlytics?

I have a project with multiple modules. The common code of the modules is in a library module. The problem is that we added recently Crashlytics to our project (in the library module), and we keep receiving error reports even when we are in Debug mode. I searched on the internet and I found out that a library is always seen as a Release mode. Now my question is, is there a way to disable Crashlytics in my case?

感谢

推荐答案

在我的应用程序(一个模块,多种口味),我发现的味道,只有在我想要的口味初始化Crashlytics。

In my app (a single module, multiple flavors), I detect the flavor, and only initialize Crashlytics in the flavors that I want.

在我而言,我一个变量添加到风味的build.gradle,像这样:

In my case, I add a variable to the flavor in build.gradle , like so:

productFlavors {
        Dev { // i.e. gradlew assembleDevDebug
            buildConfigField 'Boolean', 'enableCrashlytics', 'false'
        }

        Qa { // i.e. gradlew assembleQaDebug
            buildConfigField 'Boolean', 'enableCrashlytics', 'true'
        }
}

然后,在我的应用程序类,我有条件启动Crashlytics:

Then, in my Application class, I conditionally start Crashlytics:

if(BuildConfig.enableCrashlytics == true) {
   Fabric.with(this, new Crashlytics());
}

这篇关于Android的禁用Crashlytics在图书馆项目进行调试的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆