简体   繁体   English

Firebase Crashlytics 控制台不再显示新版本或旧版本的崩溃

[英]Firebase Crashlytics Console not showing crashes on neither new or old builds anymore

i am having an issue with firebase Crashlytics where crashes are not showing up but the crash free rate percentage is.我遇到了 firebase Crashlytics 的问题,其中没有出现崩溃,但无崩溃率百分比是。

The Problem问题

One day, on what seemed like a random day, all Crashlytic logs stopped showing up on the Firebase Crashlytics console.有一天,在看似随机的一天,Firebase Crashlytics 控制台上停止显示所有 Crashlytic 日志。 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).我假设他们确实得到了一些数据,因为为了计算这个无崩溃百分比,他们需要崩溃日志数据(也许不是,idk)。

To add to this, older builds where crashes used to be seen , also stopped showing the crash logs in the Firebase Crashlytics console.要添加到这一点,旧的构建,其中用于崩溃待观察,也停止显示在火力地堡Crashlytics控制台的崩溃日志。 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)检查我们是否更改了与 firebase crashlytics 相关的任何内容(除了更新到最新版本)
  • Updating to the latest firebase Crashlytics version (multiple times)更新到最新的 Firebase Crashlytics 版本(多次)
  • Ive tried comparing the google-services.json file to the one we have in the project, and it is the same.我试过将 google-services.json 文件与我们项目中的文件进行比较,结果是一样的。
  • 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.联系 firebase 团队,已经处理了几个星期,但仍然无法解决,我发送了日志、代码片段以及他们要求的所有内容。 But still no solution.但仍然没有解决办法。
  • Made sure we no longer have any references to the old crashlytics/fabric plugin/implementation.确保我们不再引用旧的 crashlytics/fabric 插件/实现。

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:现有的 Crashlytics 配置:

Project level build.gradle项目级 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应用级 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) (清理后仅显示与 firebase 相关的)


Note: We have our google-services.json located in the proper location in our project, as it always been.注意:我们将 google-services.json 放在我们项目中的正确位置,就像往常一样。

Was hoping someone else would be able to help.希望其他人能够提供帮助。 Thanks in advance!提前致谢!

In the new version of Firebase crashlytics (after migration from fabric) , reports of IPs of countries that are under the sanctions of Google are not visible in the console.在新版 Firebase crashlytics(从结构迁移后)中,控制台中看不到受 Google 制裁的国家/地区的 IP 报告。 This may be someone's problem.这可能是某人的问题。

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 crashlytics自定义崩溃报告未显示在Firebase控制台上 - crashlytics custom crash reporting not showing on Firebase Console Firebase Crashlytics 控制台未显示崩溃日志 - Firebase Crashlytics Console not showing crash logs 如何在 Firebase Crashlytics 控制台中过滤用户 ID 的日志事件和崩溃? - How to filter log events and crashes in Firebase Crashlytics Console for user id? classnotfound崩溃没有出现在崩溃现象中,但是在Google Play控制台中 - classnotfound crashes not showing up in crashlytics, but in google play console Firebase Crashlytics 未报告崩溃 - Firebase Crashlytics not reporting crashes Firebase/Crashlytics 仪表板未显示任何针对 android 的测试崩溃 - Firebase/Crashlytics Dashboard not showing any test crashes for android 新的 crashlytics (com.google.firebase.crashlytics.FirebaseCrashlytics) 在非 Google Play 设备上不再运行? - New crashlytics (com.google.firebase.crashlytics.FirebaseCrashlytics) not working anymore on non-Google Play devices? 几个月前用旧应用和新应用重现:Crashlytics 没有报告旧应用中的崩溃或注册我的新应用 - Reproduced months ago with old apps and new: Crashlytics was not reporting crashes in old apps or registering my new apps Firebase Crashlytics SDK 更新不起作用。 报告未显示在控制台中 - Firebase Crashlytics SDK update not working. Reports not showing in console 新的Google开发人员控制台崩溃导致堆栈跟踪不再准确 - New Google developer console crashes stack traces are not accurate anymore
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM