android – Fabric Debug Craslytic Reports : Signup, build Id missing, apply plugin : io.fabric-ThrowExceptions

Exception or error:

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 :

Gradle version :
classpath ‘’

Plugin :
Fabric for Android studio v4.3.0

Implementation :
implementation(‘’) { transitive = true }
implementation(‘’) { transitive = true } :

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,

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())

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
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:” 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'), ''
    release {
        minifyEnabled false
        proguardFiles getDefaultProguardFile('proguard-android.txt'), ''
        manifestPlaceholders = [crashlyticsEnabled: false]


2. Enable in Manifest

    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.

How to solve:

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

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 ''

    // NOTE: Do not place your application dependencies here; they belong
    // in the individual module build.gradle files
    classpath "$google_services_version" // google-services plugin

    classpath "$fabric_tools_version"


apply plugin: "io.fabric"

And finally: implementation ""

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:

google-services.json (for flavor1)

google-services.json (for flavor2)

And that’s it. Hope this helps someone.


This also happens if you set ext.enableCrashlytics = false for a build variant but still try to call Fabric.with(context, Crashlytics()) in your app initialization code. ext.enableCrashlytics = false disables the build plugin (an optimization I made to make my debug builds faster) but then of course the build ID will be missing.


Today I migrated from Fabric Crashlytics to Firebase Crashlytics and encountered a fatal error that didn’t keep me going. What I did was this:
In app-> build.gradle:

apply plugin: 'io.fabric'
dependencies {
 implementation ""
// Add dependency
implementation ''

In general build.gradle:

buildscript {

repositories {

    maven {
        url ''
dependencies {
    classpath ''  // Crashlytics plugin

And of course download the json file from Firebase and insert it in the app folder.

After completing these simple steps, I received this error when I started the application

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.

I went to check that there wasn’t any code that could call up old Fabric methods, and in fact I discovered that in app-> build.gradle I had this:

buildTypes {

    debug {
        minifyEnabled false
        debuggable true
        **ext.enableCrashlytics = false**
        ext.alwaysUpdateBuildId = false

ext.enableCrashlytics = false certainly it was a method that referred to the old Fabric, so I removed this line and everything worked perfectly! I hope to help someone with this


just set apply plugin: 'io.fabric' in ur build.gradle (app)


I had the same problem in my app (Android Studio 3.4.1)

I fixed trough conecting to the Fabric Plugin. Creating an account and linking my app to it.


In my case i just update implementation '' to implementation ''
and added apply plugin: 'io.fabric' to my app level gradle. This solved Error 2 for me.

Leave a Reply

Your email address will not be published. Required fields are marked *