Google Play 控制台报告未发布的应用程序崩溃

本文介绍了Google Play 控制台报告未发布的应用程序崩溃的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我想分享一个我在分析 Google Play 控制台的新功能时遇到的情况，并尝试找到解决方案.

I would like to share a situation I am facing analysing the new features at Google Play console and try to find a solution for it.

许多人可能已经知道，Google 已经在 Google Play 控制台上发布了更新并引入了 Android Vitals.一个好的特点是现在会话 ANRs &崩溃显示所有 ANR 和从用户选择自动共享使用情况和诊断数据的 Android 设备收集的崩溃信息(在手机首次设置期间).

As many of you may already know, Google has released updates at Google Play console and introduced Android vitals. One of the good particularities is that now the session ANRs & Crashes shows all ANRs & crashes collected from Android devices whose users have opted in to automatically share usage and diagnostics data (during phone first setup).

但是，我看到来自未发布应用程序的崩溃报告.我的意思是，来自尚未发布的开发人员版本.此外，这个崩溃报告来自一个使用 android-debug 密钥签名的应用程序，而不是我的生产密钥.我查看了可用的文档，但找不到有关过滤这些报告的详细信息.

However, I am seeing crash reports from unreleased applications. I mean, from a developer version that hasn't been published yet. Moreover, this crash report came from an application signed with an android-debug key, not my production key. I have looked into the available documentation but I couldn't found details on the filtering for these reports.

在没有验证签名的情况下使用任何收入数据对我来说似乎是有害和错误的，因为任何人都可以简单地编写一段简短的代码并开始用大量虚拟堆栈跟踪淹没特定的应用程序包名称.

It seems harmful and wrong to me using any income data without validating signing as anyone can simply write a short peace of code and start flooding a specific application package name with tons of dummy stacktraces.

你知道这是否是这个新工具的正常行为吗?

Do you know if this is the normal behavior for this new tool ?

推荐答案

由于我们有兴趣只发布发布应用程序，我们可以采用以下策略来摆脱混乱的崩溃报告:

As we are interested in publishing only release applications, we may adopt following strategy to get rid of messing up crash reports :

./build.gradle:

./build.gradle :

android { ... defaultConfig { applicationId "my.app.package" ... } ... buildTypes { release { ... } debug { ... applicationIdSuffix ".dev" } } ... }