应用程序在发布到 Google Play 后立即崩溃 [英] Burst of app crashes immediately after publishing to Google Play

查看:25
本文介绍了应用程序在发布到 Google Play 后立即崩溃的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在 Google Play 上发布应用程序的新版本后,我立即收到来自名为unknown Full Android on Emulator"的未知设备的新崩溃.

Immediately after publishing a new version of an application on Google Play, I get a burst of new crashes from an unknown device called "unknown Full Android on Emulator".

这是应用程序上传到 Google Play 后 Crashlytics 的屏幕截图.此崩溃并非来自真实设备.

Here is a screenshot from Crashlytics after the application was uploaded to Google Play. This crash did not come from a real device.

有人知道这个模拟器是什么吗?

Does anyone know what this emulator is?

Crashlytics 控制台:

Crashlytics console:

在 Splunk 控制台的此屏幕剪辑中可以看到类似的崩溃模式:

A similar pattern of crashes can be seen in this screen clip from the Splunk console:

推荐答案

自从发布新版本后,我看到几乎只有这台设备崩溃了,我猜这是一个 Google Play 新应用发布流程,他们在其中 monkey 测试您的应用程序.

Since soon after publishing a new version I see crashes almost only from this device, I'm guessing it's a Google Play new app publishing flow, where they monkey test your app.

我看到无法在 UI 中打开但可以通过直接 Intent 访问的 Debug 活动崩溃,所以我也猜测这个猴子测试会遍历清单,直接启动随机活动,并且和他们一起玩.

I'm seeing crashes from Debug activities that can't be opened in the UI, but can be accessed via a direct intent, so I'm also guessing this monkey test goes over the manifest, launches random activities directly, and plays with them.

参见:http://developer.android.com/tools/help/monkey.html

这篇关于应用程序在发布到 Google Play 后立即崩溃的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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