带有 Firebase 的 Fabric crashlytics 无法上传崩溃答案

【问题标题】：Fabric crashlytics with Firebase unable to upload crash带有 Firebase 的 Fabric crashlytics 无法上传崩溃
【发布时间】：2018-08-29 11:58:32
【问题描述】：

我只是想用 Firebase 迁移 Fabric Crashlytics，所以我只是按照指南 https://firebase.google.com/docs/crashlytics/get-started

一切都编译好了，应用程序就可以启动了。所以我想用我以前用过的Crashlytics.getInstance().crash(); 模拟崩溃。

应用程序按预期崩溃，但崩溃未上传到 firebase，我有这个奇怪的堆栈：

E/Fabric: Error performing auto configuration.
                                               io.fabric.sdk.android.services.network.HttpRequest$HttpRequestException: java.net.ProtocolException: Too many follow-up requests: 21
                                                   at io.fabric.sdk.android.services.network.HttpRequest.code(HttpRequest.java:1355)
                                                   at io.fabric.sdk.android.services.settings.AbstractAppSpiCall.invoke(AbstractAppSpiCall.java:86)
                                                   at io.fabric.sdk.android.services.settings.UpdateAppSpiCall.invoke(UpdateAppSpiCall.java:29)
                                                   at io.fabric.sdk.android.Onboarding.performUpdateApp(Onboarding.java:204)
                                                   at io.fabric.sdk.android.Onboarding.performUpdateApp(Onboarding.java:194)
                                                   at io.fabric.sdk.android.Onboarding.performAutoConfigure(Onboarding.java:175)
                                                   at io.fabric.sdk.android.Onboarding.doInBackground(Onboarding.java:112)
                                                   at io.fabric.sdk.android.Onboarding.doInBackground(Onboarding.java:45)
                                                   at io.fabric.sdk.android.InitializationTask.doInBackground(InitializationTask.java:63)
                                                   at io.fabric.sdk.android.InitializationTask.doInBackground(InitializationTask.java:28)
                                                   at io.fabric.sdk.android.services.concurrency.AsyncTask$2.call(AsyncTask.java:311)
                                                   at java.util.concurrent.FutureTask.run(FutureTask.java:237)
                                                   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)
                                                   at java.util.concurrent.FutureTask.run(FutureTask.java:237)
                                                   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
                                                   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
                                                   at java.lang.Thread.run(Thread.java:762)
                                                Caused by: java.net.ProtocolException: Too many follow-up requests: 21
                                                   at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getResponse(HttpURLConnectionImpl.java:451)
                                                   at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getResponseCode(HttpURLConnectionImpl.java:567)
                                                   at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.getResponseCode(DelegatingHttpsURLConnection.java:105)
                                                   at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java)

有人遇到过这个错误吗？

【问题讨论】：

Retrofit - Too many follow-up requests: 21的可能重复
谢谢。你还在遇到这种情况吗？
我必须创建 fabric.properties 文件并输入 api 密钥才能使其工作
@ToddBurner 即使我们迁移到firebase，我们还需要添加api密钥吗？
@ToddBurner up?

标签： android firebase crashlytics google-fabric

【解决方案1】：

当您从 Fabric 迁移到 Firebase Crashlytics 时从 Fabric 中剥离 API 密钥时，可能会发生这种情况，目前尚不支持。迁移时，请将您的 API 密钥保留在您的项目中。

【讨论】：