question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Crashlytics console not showing any crashes anymore

See original GitHub issue

The Problem

All Crashlytic logs randomly stopped showing up on the Firebase Crashlytics console. The crash free rate percentage, however, does show up there. I assume that they are indeed getting some data, because in order to calculate this crash free percentage they need the crash log data (maybe not, idk).

To add to this, older builds where crashes used to be seen, also stopped showing the crash logs in the Firebase Crashlytics console. At this point i am convinced that it might not be a configuration issue on our end, if it was older builds shouldnt be affected.

There are no error logs either, telling us that something is wrong.

What i have tried

Checked to see if we changed anything related to firebase crashlytics (besides updating to the latest version) Updating to the latest firebase Crashlytics version (multiple times) Ive tried comparing the google-services.json file to the one we have in the project, and it is the same. Contacting the firebase team, been at it for a few weeks now and still could not resolve, ive sent the logs, code snippets, everything they asked for. But still no solution. Made sure we no longer have any references to the old crashlytics/fabric plugin/implementation. Project info:

  • Kotlin version: 1.4.10
  • Gradle plugin version: 4.0.2
  • firebase-crashlytics-gradle version: 2.3.0
  • Firebase Crashlytics version: 17.2.2

Existing Crashlytics configuration:

Project level build.gradle

// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {

    repositories {
        google()
        jcenter()
        maven { url 'https://plugins.gradle.org/m2/' }
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:4.0.2'
        classpath "com.apollographql.apollo:apollo-gradle-plugin:1.2.0"
        classpath group: 'commons-io', name: 'commons-io', version: '2.5'
        classpath 'com.google.gms:google-services:4.3.4'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.4.10"
        classpath 'com.google.firebase:perf-plugin:1.3.2'
        classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0'
    }
}

allprojects {
    repositories {
        google()
        mavenCentral()
        jcenter()
        maven { url 'https://jitpack.io' }
    }
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

App level build.gradle

import groovy.json.JsonOutput
import org.apache.commons.io.IOUtils

apply plugin: 'com.android.application'
apply plugin: 'com.google.firebase.firebase-perf'
apply plugin: 'com.google.firebase.crashlytics'
apply plugin: 'kotlin-android'
apply plugin: 'kotlin-kapt'
apply plugin: 'kotlin-android-extensions'

if (project.hasProperty("enableJacoco")) {
    apply from: '../jacoco.gradle'
}

repositories {
    maven { url 'https://www.jitpack.io' }
    flatDir {
        dirs 'libs'
    }
}

androidExtensions {
    experimental = true
}

android {
    compileSdkVersion 29
    buildToolsVersion "29.0.2"
    defaultConfig {
        applicationId "com.my-app"
        minSdkVersion 21
        targetSdkVersion 29

        testInstrumentationRunner "com.my-app.TestAppJUnitRunner"

        vectorDrawables.useSupportLibrary = true

        // for auto factory
        javaCompileOptions {
            annotationProcessorOptions {
                includeCompileClasspath = true
            }
        }
    }

    buildTypes {
        release {
            minifyEnabled true
            zipAlignEnabled true
            debuggable false
            testCoverageEnabled false

            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
        debug {
            FirebasePerformance {
                instrumentationEnabled false
            }
            debuggable true
            testCoverageEnabled project.hasProperty("enableJacoco")

            firebaseCrashlytics {
                mappingFileUploadEnabled false
            }
        }
    }

    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
        // Flag to enable support for the new language APIs
        coreLibraryDesugaringEnabled true
    }

    useLibrary 'android.test.runner'
    useLibrary 'android.test.base'
    useLibrary 'android.test.mock'
}

dependencies {

    // Firebase
    implementation "com.google.firebase:firebase-messaging:20.1.0"
    implementation "com.google.firebase:firebase-core:17.2.0"
    implementation "com.google.firebase:firebase-perf:19.0.0"
    implementation "com.google.firebase:firebase-auth:19.2.0"

    implementation "com.google.firebase:firebase-analytics:17.6.0"
    implementation "com.google.firebase:firebase-crashlytics:17.2.2"
    
}

apply plugin: 'com.google.gms.google-services'

(cleaned up to show firebase related only)

Note: We have our google-services.json located in the proper location in our project, as it always been.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:4
  • Comments:27 (12 by maintainers)

github_iconTop GitHub Comments

2reactions
mrwillis21commented, Dec 11, 2020

@tspecht Alright cool. Well, not cool, but thanks for the info. 😝 I’ll report back when I have more information for you.

1reaction
luispereiracommented, Dec 10, 2020

Just tested this and it seems to be reporting to the firebase console now

For anyone experiencing this using Dexguard, please update to the latest 8.x version or add this to your obfuscation rules:

-keepresourcexmlelements manifest/application/service/meta-data@value=cct

That should address the issue for future versions of your app.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Firebase Crashlytics Console not showing crashes on neither ...
The Problem​​ I assume that they are indeed getting some data, because in order to calculate this crash free percentage they need the...
Read more >
Crashlytics troubleshooting and FAQ - Firebase
Not seeing crash -free users, breadcrumb logs, and/or velocity alerts; dSYMs are missing/not uploading; Crashes are poorly symbolicated; How are crash-free ...
Read more >
[Solved]-Firebase Crashlytics console not showing crashes
User reached out to Firebase customer support. The issue had to do with illegal characters in the form of whitespace being present in...
Read more >
Crashlytics in the Firebase Console
If you are certain that your app has produced error reports, but none are visible, try restarting your app fully. Crashlytics only uploads...
Read more >
crashlytics | B4X Programming Forum
Crashlytics is only good when the app actually crashes, but if the error is managed and ... Hi all, I've a problem with...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found