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:
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.
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"
来源：https://stackoverflow.com/questions/26346336/burst-of-app-crashes-immediately-after-publishing-to-google-play