小编Hos*_*pes的帖子

我有Frabric(Crashlytics)服务的神秘问题.
我发现crashlytics不会自动对崩溃日志进行去模糊处理.

顶级构建文件中的io.fabric.tools版本1.19.1和android.tools版本1.2.3:

dependencies {
    classpath 'com.android.tools.build:gradle:1.2.3'
    classpath 'io.fabric.tools:gradle:1.19.1'
}

BuildTypes配置:

buildTypes {
    debug{
        debuggable true
        jniDebuggable true
    }
    release {
        debuggable false
        jniDebuggable false
        minifyEnabled true
        proguardFiles 'proguard-coda.txt', 'proguard-rules.pro'
    }
}

和依赖:

compile('com.crashlytics.sdk.android:crashlytics:2.4.0@aar') {
    transitive = true
}

proguard配置文件包含:

-renamesourcefileattribute SourceFile
-keepattributes SourceFile,LineNumberTable

从gradle控制台我看到与crashlytics相关的任务是可以的,:app:crashlyticsStoreDeobsRelease并且:app:crashlyticsUploadDeobsRelease:

Executing tasks: [:app:assembleRelease]

Configuration on demand is an incubating feature.
:app:preBuild UP-TO-DATE
:app:preReleaseBuild UP-TO-DATE
:app:checkReleaseManifest
:app:preDebugBuild UP-TO-DATE
...............................
:app:fabricGenerateResourcesRelease
:app:processReleaseResources
:app:generateReleaseSources
:app:processReleaseJavaRes UP-TO-DATE
:app:compileReleaseJava UP-TO-DATE
:app:compileReleaseNdk UP-TO-DATE
:app:compileReleaseSources UP-TO-DATE
:app:collectReleaseMultiDexComponents UP-TO-DATE …