Firebase崩溃报告错误:客户端应用程序com.xxxx被阻止 [英] Firebase Crash Reporting error: client application com.xxxx are blocked

问题描述

我已经在项目中成功实施了FCM和Firebase分析，但是尝试使用Firebase崩溃报告时发现错误，我不知道自己缺少什么.

I have implemented FCM and Firebase analytics with success in my project but I found an error trying with Firebase crash reporting and I don't have any idea what I'm missing.

我只是在官方教程之后尝试使用Firebase崩溃报告，并且出现此错误:
它说:

I'm just trying to use Firebase crash reporting following the official tutorial and getting this error:
It said:

服务器未收到报告:起源错误消息:来自此Android客户端应用程序com.xxxxxx 的请求被阻止.

在Google和此处进行挖掘(堆栈溢出)后，我发现了一些相关问题( 链接1 ， 链接2 ， 链接3 )，但它们的解决方案都不适合我.我的意思是，有人谈论Check API_KEY，有人谈论在控制台中启用的Check crash报告，并且列表还在继续.在发布此问题之前，我已经尝试过这些答案.

After dig in google and here (stack overflow), I found some related questions ( link 1, link 2, link 3) but none of their solutions work for me. I mean, someone talk about check API_KEY, someone else talk about check crash report enabled in console and the list keep going. I have tried those answers before posting this question.

更新:为那些不想看上面链接的用户解释一下:我尝试更新google-services.json文件，更改API_KEY，删除并再次添加SHA1，将API_KEY保留为空等等.对于我所做的每项更改，都需要下载google-services.json文件.

update: Explaining a little bit for those didn't want to look above links: I tried updating the google-services.json file changing the API_KEY, deleting and adding again SHA1, leaving API_KEY empty, etc. Downloading the google-services.json file for each change I did with no luck.

我的google-services.json文件中的API_KEY如下:

My API_KEY in my google-services.json file looks like:

"api_key": [
    {
      "current_key": "AIzaxxxxxxxxxxzxxxxxx"
    },
    {
      "current_key": "AIzaxxxxxxxxxxxxxx"
    }
  ],

然后我检查了google-service.json是否已调试并释放SHA1.

And I checked that my google-service.json has debug and release SHA1.

更新 奇怪的是，我在Google Analytics(分析)部分中获取报告，如您在下一个屏幕截图中所见:

update The weird thing is that I'm getting reports in Analytics section, as you can see in next screenshot:

在 console.developers.google.com 中查看项目，我发现我有移动崩溃和效果报告已启用的API(如您在以下屏幕截图中所见):



单击"Mobile Crash and Performance Reporting API"后，我得到了以下信息: 上方的图片显示了2张图片:"Mobile Crash and Performance Reporting API"的所有流量都已完成，API处理了错误.如您所见，它说我的所有请求都是 403错误(您可以在它显示403:0.0004的地方看到它):的确，我已经尝试了4次，而且每次都使用同一个控制台错误.

Looking the project in console.developers.google.com I found that I have Mobile Crash and Performance Reporting API enabled (like you can see in the follow screenshot):



After clicking in "Mobile Crash and Performance Reporting API" I got this: The image above shows 2 images: all traffic to "Mobile Crash and Performance Reporting API" done and the errors processed by the API. As you can see it said that all my request were 403 Error (you can see it where it said 403:0.0004): and that's true, I've tried 4 times and all time I got same console error.

不知道发生了什么或我错过了什么

如果您需要有关gradle应用程序文件的信息来帮助我，请访问:

If you need info about gradle app file to help me, here is:

编译'com.google.firebase:firebase-core:10.0.1'
编译'com.google.firebase:firebase-messaging:10.0.1'
编译'com.google.firebase:firebase-crash:10.0.1'
编译'com.google.android.gms:play-services-maps:10.0.1'
编译'com.google.android.gms:play-services-location:10.0.1'
编译'com.google.android.gms:play-services-awareness:10.0.1'

compile 'com.google.firebase:firebase-core:10.0.1'
compile 'com.google.firebase:firebase-messaging:10.0.1'
compile 'com.google.firebase:firebase-crash:10.0.1'
compile 'com.google.android.gms:play-services-maps:10.0.1'
compile 'com.google.android.gms:play-services-location:10.0.1'
compile 'com.google.android.gms:play-services-awareness:10.0.1'

推荐答案

我遇到了同样的问题，可以通过将Google控制台中的API密钥Key restriction设置为NONE来解决.

I had the same issue, solved it by setting the API key Key restriction in Google Console to NONE.

这篇关于Firebase崩溃报告错误:客户端应用程序com.xxxx被阻止的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！