Menu
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".
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 console:
A similar pattern of crashes can be seen in this screen clip from the Splunk console:
576
Improper App installation can cause Android Apps to crash. You must download the App from the Google Play Store and only use it once it is successfully and completely installed on your device. If your Apps stops abruptly, delete, or uninstall the App from your device and reinstall it after a few minutes.
Select an app. On the left menu, select Quality > Android vitals > Crashes and ANRs. Near the center of your screen, use the filters to help you find and diagnose issues. Alternatively, select a cluster to get more details about a specific crash or ANR error.
The easiest way to fix an app that keeps crashing on your Android smartphone is to simply force stop it and open it again. To do this, go to Settings -> Apps and select the app that keeps crashing. Tap on the app's name and then tap on 'Force stop'. Now try opening the app again and see if it works well.
When the UI thread of an Android app is blocked for too long, an "Application Not Responding" (ANR) error is triggered. If the app is in the foreground, the system displays a dialog to the user, as shown in figure 1. The ANR dialog gives the user the opportunity to force quit the app.
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.
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.
See: http://developer.android.com/tools/help/monkey.html
97
I also found similar issue reported on Crashlytics with a Rooted Emulator , and it's NullPointer Exception in onCreate() of an activity when I try to access a value got from getIntent(). But I always put this value in previous activity . So I guess it's launch by monkey or "adb am start" even the activity is exported = "false"
38
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
