【问题标题】:Firebase Console still show Crashlytics Implementation DialogFirebase 控制台仍显示 Crashlytics 实施对话框
【发布时间】:2018-09-26 07:13:13
【问题描述】:

按照文档中的说明实施 https://firebase.google.com/docs/crashlytics/get-started?authuser=0

buildscript {

repositories {
    google()
    jcenter()
    maven { url 'https://maven.fabric.io/public' }
}
dependencies {
    classpath 'com.android.tools.build:gradle:3.1.4'
    classpath 'com.google.gms:google-services:4.0.1'
    classpath 'io.fabric.tools:gradle:1.25.4'
    // NOTE: Do not place your application dependencies here; they belong
    // in the individual module build.gradle files
}
}
allprojects {
    repositories {
        google()
        jcenter()
        maven {
            url 'https://maven.google.com/'
        }
    }
}

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

模块:应用程序

apply plugin: 'com.android.application'
apply plugin: 'io.fabric'

......
......
dependencies {
    ........
    ........

    implementation 'com.google.firebase:firebase-core:16.0.3'
    implementation 'com.google.firebase:firebase-messaging:17.3.2'
    implementation 'com.startapp:inapp-sdk:3.10.1'
    implementation 'com.crashlytics.sdk.android:crashlytics:2.9.5'
    implementation 'com.google.firebase:firebase-crash:11.8.0'
}
apply plugin: 'com.google.gms.google-services'

在主要的 Laucher 活动中

@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);

    /*StartAppSDK.init(this, getResources().getString(R.string.startApp_sdk), false);
    StartAppAd.disableSplash();*/

    setContentView(R.layout.activity_permission);

//Both Tried But Not get Any result

    Fabric.with(this, new Crashlytics());
   /*final Fabric fabric = new Fabric.Builder(this)
            .kits(new Crashlytics())
            .debuggable(true)  // Enables Crashlytics debugger
            .build();
    Fabric.with(fabric);*/
    FirebaseCrash.log("Activity created");
  }
}

我试过手动崩溃

Crashlytics.getInstance().crash(); // Force a crash

我的问题是 Firebase 控制台仍然显示实施对话框

为什么在 2 小时前就已经实施了?

崩溃后的应用程序日志看起来像......只是为了测试 Basb,我从 Manifest 文件中删除了我的 MainActivity。错误如期而至,但 Firebase 控制台仍显示实施对话框。为什么?

D/CrashlyticsCore: Crashlytics is handling uncaught exception "android.content.ActivityNotFoundException: Unable to find explicit activity class {com.gauravkhannamarketeer.navratriwallpaperapp/com.gauravkhannamarketeer.navratriwallpaperapp.activity.MainActivity}; have you declared this activity in your AndroidManifest.xml?" from thread main
D/Answers: Logged crash
D/SensorManager: sensorCTSV isCtsVerifier false
                 sensorCTSV isCtsVerifier false
                 sensorCTSV isCtsVerifier false
D/CrashlyticsCore: No log data to include with this event.
D/CrashlyticsCore: Closing open sessions.
                   Closing session: 5BAB3C570014-0001-7C73-036ED06B5023
                   Collecting session parts for ID 5BAB3C570014-0001-7C73-036ED06B5023
D/CrashlyticsCore: Session 5BAB3C570014-0001-7C73-036ED06B5023 has fatal exception: true
                   Session 5BAB3C570014-0001-7C73-036ED06B5023 has non-fatal exceptions: false
D/CrashlyticsCore: Collecting SessionStart data for session ID 5BAB3C570014-0001-7C73-036ED06B5023
D/CrashlyticsCore: Collecting SessionUser data for session ID 5BAB3C570014-0001-7C73-036ED06B5023
D/CrashlyticsCore: Collecting SessionApp data for session ID 5BAB3C570014-0001-7C73-036ED06B5023
D/CrashlyticsCore: Collecting SessionOS data for session ID 5BAB3C570014-0001-7C73-036ED06B5023
D/CrashlyticsCore: Collecting SessionDevice data for session ID 5BAB3C570014-0001-7C73-036ED06B5023
D/CrashlyticsCore: Removing session part files for ID 5BAB3C570014-0001-7C73-036ED06B5023
D/CrashlyticsCore: Opening a new session with ID 5BAB3C9403A8-0002-7C73-036ED06B5023
D/CrashlyticsCore: Crashlytics completed exception processing. Invoking default exception handler.

【问题讨论】:

  • 尝试删除折旧的依赖:com.google.firebase:firebase-crash:11.8.0 并且只使用:Crashlytics
  • 感谢您的回复,但无法正常工作 stll 显示 imlemetation 对话框@ʍѳђઽ૯ท
  • 更新谷歌服务怎么样? classpath 'com.google.gms:google-services:4.1.0'
  • 确定我会在几秒钟内更新它
  • 这很奇怪。删除旧的com.google.firebase:firebase-crash 并更新谷歌服务应该可以解决问题。但是,您可以从Tools -> Firebase 检查crashlytics 是否配置良好,它是否显示相同。另外,您可以查看this sample

标签: android firebase crashlytics crash-reports


【解决方案1】:

顺便说一下,主要问题仍在继续,但我通过使用 android studio fabric 插件转移到结构实现来解决它

面料

通过您的 IDE 存储库下载“Fabric for Android”。 Mac 用户:从 Android Studio / IntelliJ 菜单中选择“首选项...”。 Windows 和 Linux 用户:从文件菜单中选择“设置”。

选择“设置”对话框左侧的“插件”。选择“浏览存储库...”

搜索“Fabric for Android”并安装插件。

IDE重启后,点击Fabric工具栏按钮开始使用Fabric!

【讨论】:

  • 那是一团糟,不要使用 Fabric 插件。这不是任何灵魂。仅使用 Firebase 控制台并按照说明进行操作。
  • @user1209216 先生,你是对的,但我按照织物文档解释的说明进行操作
猜你喜欢
  • 2020-01-03
  • 2020-12-27
  • 2018-04-20
  • 1970-01-01
  • 2021-08-24
  • 1970-01-01
  • 1970-01-01
  • 2021-09-23
  • 1970-01-01
相关资源
最近更新 更多