For the last two APKs I have uploaded to play console the android pre launch report is showing "Devices with issues 9" under "Stability tab" but then in the individual break down each device has 0 issues. Any explanation to this? Is this APK safe to launch?
Play console screenshot
Try to check the same report in the new console. It seems some data may differ.
New console: https://play.google.com/console/developers/
Related
I have a problem with an Android App that I have on the Android Play Store. In the Google Play ANRs & crashes report, there are reports coming from tests that I have done myself during my developments in Android Studio.
I’m sure of that because the model of the phone corresponds to my phone and the line where the crash occurred didn’t exist at all in the last release.
I would like to know if there is a way to avoid such problem. When doing developments in Android Studio, shall I change something to be sure that any crash that I generate during my tests will not be sent to Google Play ANRs & crashes report?
I would like reports to be sent only for signed releases.
Thanks for your help
I recently uploaded my app to the Google Play Store but got this pre-launch report in some devices :
Issue: Crash of app com.mypackage running instrumentation
ComponentInfo{com.google.android.apps.mtaas.crawler/android.support.test.runner.AndroidJUnitRunner}
How do solve it ?
I got the answer in Google play Console Help
As of October 2017, the pre-launch report uses a new crawler to provide a more comprehensive review of your app. To do so, the pre-launch report must temporarily re-sign your APK within our test environment.
If you notice any issues, you can switch back to the previous testing process (which doesn't require APK re-signing):
Sign in to your Play Console.
Select an app.
Select Release
management > Pre-launch report > Settings.
In the 'Pre-launch report version' section, move the Opt-out switch to the right until it turns blue.
I have tested and all test passed for all devices, and no more crash for running instrumentation.
I'm trying to test the licencing on an app:
Uploaded the apk as an alpha to google play in the dev console
added tester emails
visited the testers' link once it was published and live
Problem: It says my device is incompatible with the app!
I debugged directly from Android Studio via usb on the same device, and when I upload the apk to my phone, I can install it directly.
Also, Google Play gives me no hints as to what the issue of obstruction is. How do I debug this issue?
In cases like this, keep an eye on the details: I had the noob error of using maxSdkVersion instead of the proper minSdkVersion - an oversight of 2 characters.
How do I check for errors or log errors in release version of my app?
Activity crashes the app in release version but working in debug version. How do I check for errors?
You have a few options before you:
1. If your app is already live, then the Play Store records all exceptions thrown by apps on connected devices. Log into your Google Play Store account and see here.
2. If you need even more detail, the Google Play Services library has deeper support for crash analysis than what you normally get from the Play Store. See here.
3. You can add a support package like Crashlytics that will provide real-time analysis for apps in the wild.
4. Log.e(), Log.v(), Log.i() and Log.wtf() emit log messages even in release mode, and can be observed in the Logcat.
Add crash reporting libraries like ACRA to check error logs in release mode.
Here is link for ACRA library
I already had a version (versioncode=2) in Google Store. Yesterday after doing some changes, when I tried publishing the app, i am getting below error message and not able to publish the updates. Any idea how can I fix it?
This configuration cannot be published for the following reason(s):
Version 2 is not served to any device configuration: all devices that might receive version 2 would receive version 3.
Some devices are eligible to run multiple APKs. In such a scenario, the device will receive the APK with the higher version code.
FYI, the new version is versioncode=3
You need to "Deactivate" the current apk in order to actually publish the new apk.
Deactivate the 2 version on the Google Play.
All this says is that version 3 is applicable for all devices that version 2 is applicable for. This means version 2 is obsolete.
If you check closely, when you upload your APK there is no option to Publish to production, only Save as Draft. This happened to me last night and drove me crazy. Now, in the morning I uploaded the new APK again and the Publish to production button was there! I don't what caused this issue but now it's fine.