Fabric Debug Craslytic Reports : Signup, build Id missing, apply plugin : io.fabric

Question

We have programming an Android app and try to implement Crashlytics to our app.

We have different types of problem . Version we used : Android studio version : 3.3

Gradle version : classpath 'com.android.tools.build:gradle:3.3.1'

Plugin : Fabric for Android studio v4.3.0

Implementation : implementation('com.crashlytics.sdk.android:crashlytics:2.9.9') { transitive = true } implementation('io.fabric.sdk.android:fabric:1.4.0@aar') { transitive = true }

gradle-wrapper.properties : distributionUrl=https://services.gradle.org/distributions/gradle-5.2.1-all.zip

First Problem :

When we implement Crashlytics, you know that developers have 3 steps. We can not skip 2,3.steps. Because we have not compiled our application yet. We had two main errors:

Error 1:

This app relies on Crashlytics. Please sign up for access at https://fabric.io/sign_up,

Error 2 :

E/CrashlyticsCore: The Crashlytics build ID is missing.This occurs when  Crashlytics tooling is absent from your app's build configuration. Please review Crashlytics onboarding instructions and ensure you have a valid Crashlytics account. 

So, we had to be disabled "Debug Mod" to complete implementation of Crashlytic.

Crashlytics crashlyticsKit = new Crashlytics.Builder()         .core(new CrashlyticsCore.Builder().disabled(BuildConfig.DEBUG).build())         .build();  Fabric.with(this, crashlyticsKit);  // Tod from Fabric suggested in stackoverflow 

And implementation was completed.

But we do not want to do that. Because, when we have a crash, it does not any report to Crashlytics or Firebase. We also want to have debug mod’s crashes.

When we removed -> ....disabled(BuildConfig.DEBUG) - it shows again : Error 1, Error 2.

Second Problem :

In gradle ; apply plugin : ‘io.fabric’, we made the comment line, when we remove comments line, we have errors below :

Error 3 :

WARNING: API 'variant.getExternalNativeBuildTasks()' is obsolete and has been replaced with 'variant.getExternalNativeBuildProviders()'. It will be removed at the end of 2019. For more information, see https://d.android.com/r/tools/task-configuration-avoidance. To determine what is calling variant.getExternalNativeBuildTasks(), use -Pandroid.debug.obsoleteApi=true on the command line to display a stack trace. Affected Modules: app 

When we searched it, this error related to new android studio gradle. So we needed to make comment line “apply plugin: fabric.io” again.

There is no good solution about that.

To run application we can not remove:

new CrashlyticsCore.Builder().disabled(BuildConfig.DEBUG).build() : (due to Error1 Error2)

So we try to enable report different ways :

What have we try to add until here?

1. Enable in gradle :

buildTypes {     debug {         manifestPlaceholders = [crashlyticsEnabled: true]         minifyEnabled false         proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'     }     release {         minifyEnabled false         proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'         manifestPlaceholders = [crashlyticsEnabled: false]      } 

2. Enable in Manifest

<meta-data     android:name="firebase_crashlytics_collection_enabled"     android:value="true" /> 

3.Enable in ADB

  adb shell setprop log.tag.Fabric DEBUG   adb shell setprop log.tag.CrashlyticsCore DEBUG 

But still, Crashlytics or Firebase does not get any Debug Crash reports.

We have expecting your solutions.

Answer 1

I managed to get this fixed without adding android.debug.obsoleteApi=true in gradle.properties.

I basically connected 3 flavors to different Firebase projects using proper flavor configuration and the provided google-services.json file.

What your gradle file is missing comparing it to mine is this:

dependencies {     classpath 'com.android.tools.build:gradle:3.2.1'      // NOTE: Do not place your application dependencies here; they belong     // in the individual module build.gradle files     classpath "com.google.gms:google-services:$google_services_version" // google-services plugin      classpath "io.fabric.tools:gradle:$fabric_tools_version"  } 

apply plugin: "io.fabric"

And finally: implementation "com.google.firebase:firebase-crash:16.2.1"

I know Fabric is going to shut down this year, but by running the apps this way, they connected to the Firebase console with no problem whatsoever.

Regarding the flavor configuration, I downloaded three different json files (I have 3 flavors) and added them in the root directory of each flavor. For example:

flavor1: assets java res AndroidManifest google-services.json (for flavor1)  flavor2: assets java res AndroidManifest google-services.json (for flavor2) 

And that's it. Hope this helps someone.

EDIT
So, as you guys may already know, Fabric is shutting down and Firebase Crashlytics is ready, making this answer deprecated.
Please check here so you can successfully update your app and avoid weird behaviors.