Crashlytics说“收到的空设置,跳过报告提交". [英] Crashlytics says "Received null settings, skipping report submission"

查看:156
本文介绍了Crashlytics说“收到的空设置,跳过报告提交".的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试从Firebase崩溃报告切换到Firebase Crashlytics.

我在这里遵循了指南: https://firebase.google.com/docs/crashlytics/upgrade-from -崩溃报告

但是在初始化过程中,日志显示:

收到空设置,跳过报告提交!

然后在测试崩溃时:

无法发送报告.设置不可用.

网络连接良好,因此没有理由无法获得设置.

日志输出:

D/CrashlyticsCore: Initialization marker file created.
W/CrashlyticsCore: Received null settings, skipping report submission!
D/CrashlyticsCore: Initialization marker file removed: true
D/CrashlyticsCore: Crashlytics is handling uncaught exception "java.lang.RuntimeException: Testing crash" from thread main
D/CrashlyticsCore: Logging Crashlytics event to Firebase
D/CrashlyticsCore: No log data to include with this event.
D/CrashlyticsCore: Unable to close session. Settings are not loaded.
D/CrashlyticsCore: Opening a new session with ID 5A042DD20217-0002-4F33-A5AF620D03D1
D/Fabric: Falling back to Crashlytics key lookup from Manifest
D/Fabric: Falling back to Crashlytics key lookup from Strings
D/Fabric: Falling back to Crashlytics key lookup from Manifest
D/Fabric: Falling back to Crashlytics key lookup from Strings
W/CrashlyticsCore: Cannot send reports. Settings are unavailable.
D/CrashlyticsCore: Crashlytics completed exception processing. Invoking default exception handler.

解决方案

从Fabric Crashlytics升级到Firebase Crashlytics时,我发现需要确保AndroidManifest.xml包含Fabric中的此属性.将Fabric中的应用正确链接到Firebase之后.您可以在 https://www.fabric.io/settings/organizations 中找到,

<meta-data
    android:name="io.fabric.ApiKey"
    android:value="..." />

(用密钥替换...) 这需要在<application>块中.一旦添加了此设置,就会检测到设置,并且崩溃会显示在Firebase控制台中,并显示电子邮件警报.

I am trying to switch from Firebase Crash reporting to Firebase Crashlytics.

I have followed the guide here: https://firebase.google.com/docs/crashlytics/upgrade-from-crash-reporting

But during initialization the logs says:

Received null settings, skipping report submission!

And then when testing crashes:

Cannot send reports. Settings are unavailable.

Network connection is good, so no reason why it can't get settings.

Log output:

D/CrashlyticsCore: Initialization marker file created.
W/CrashlyticsCore: Received null settings, skipping report submission!
D/CrashlyticsCore: Initialization marker file removed: true
D/CrashlyticsCore: Crashlytics is handling uncaught exception "java.lang.RuntimeException: Testing crash" from thread main
D/CrashlyticsCore: Logging Crashlytics event to Firebase
D/CrashlyticsCore: No log data to include with this event.
D/CrashlyticsCore: Unable to close session. Settings are not loaded.
D/CrashlyticsCore: Opening a new session with ID 5A042DD20217-0002-4F33-A5AF620D03D1
D/Fabric: Falling back to Crashlytics key lookup from Manifest
D/Fabric: Falling back to Crashlytics key lookup from Strings
D/Fabric: Falling back to Crashlytics key lookup from Manifest
D/Fabric: Falling back to Crashlytics key lookup from Strings
W/CrashlyticsCore: Cannot send reports. Settings are unavailable.
D/CrashlyticsCore: Crashlytics completed exception processing. Invoking default exception handler.

解决方案

When upgrading from Fabric Crashlytics to Firebase Crashlytics I found that I needed to make sure that AndroidManifest.xml contained this attribute from Fabric. After having correctly linked the App in Fabric with Firebase. Which you can find at https://www.fabric.io/settings/organizations,

<meta-data
    android:name="io.fabric.ApiKey"
    android:value="..." />

(Replacing ... with your key) This needs to be within the <application> block. Once I included this the settings were detected and crashes appeared in the Firebase console, email alerts.

这篇关于Crashlytics说“收到的空设置,跳过报告提交".的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆