I received this email from Google:
"App status: Your app has not been accepted into Designed for Families, and the update is not live on Google Play.
Eligibility issues:
During testing we experienced stability issues with your app and were unable to successfully evaluate it for the Designed for Families program. Please make sure your app behaves predictably at runtime and does not crash, hang, or display error messages, and resubmit."
I have tested my app in the simulator, emulator, and in a Samsung phone and it works fine. Did anyone else had this issue with Google and how did you solve it? I'm at a loss and feel like I'm on a dead end. Please help.
Related
I created an app and it’s live in Google Play. I constantly test it to eliminate bugs and crashes. The app is almost crash-free. But sometimes I receive bad reviews from my users (only Samsung devices users) (1-2% of Samsung devices). They say that the app opens but displays a screen with app title and gets stuck on it (I don’t even have such screen in my app).
I am not receiving any crash reports or ANR reports about something that can be related to this issue. I tested on all Samsung devices I could find (friends, relatives, hired people on Upwork) but everything just works fine.
Is there anything that can cause this issue?
Maybe somewhere in your code does not work on those devices or there is an exception you caught but forgot to log it.
Try analyzing your logs and use some services like Microsoft Appcenter to find out which part of your app does not work properly.
An app I published crashes on certain specific devices. I keep receiving messages from the users that just "can't open" the app. This of course lowers the rating on Google Play.
On Android Vitals there's no reference of these crashes, all crashes I receive are managed and happen after the app start, but if I filter for device model or Android version looking for those that tell me that the app didn't open, I find absolutely NOTHING.
I installed crashlytics, and I was astonished by the fact that I received completely different error communications, so Android Vitals seems just partial?
And anyway, still NOTHING about early crashes.
I tried to install the app on the official Samsung online emulator for some devices that are suspected to crash, and still... guess... NOTHING. So I can't even test it and I'm completely helpless.
How can I do to stop this bad app behaviour, that reduces the number of my happy users? I need a really reliable way to detect ALL crashes.
thank you.
Use a Crash Reporting Tool such as Firebase Crash Reporting. Everyone professional uses such tool
https://firebase.google.com/docs/crash/
As already mentioned, you can use a crash reporting tool/framework, additionally you should be aware, that offline crashed might not get reported and if the user doesn't allow you to use the internet, there is no way around that, as far as I'm aware.
In the meantime you could try excluding the devices that you suspect to produce crashed while you are trying to fix it (if you care about the rating).
I submitted my first android wear watch face to the Play store last night, but it got rejected. The reason in the email was simply:
Eligibility issues:
-Basic functionality of your app does not work as described. Be sure to test your app on a variety of different Android Wear devices and
configurations.
Please refer to the following developer pages for details:
https://developer.android.com/tools/testing/index.html
https://developer.android.com/training/building-wearables.html
How can I find out more? It works fine on my own watch, and a friend with a different watch tried it and it was also fine. I've tried it on the emulator with a few other screen sizes, and it works there too. I don't see anything in the developer console that lets me see what tests they did that failed, so I don't know what to do to fix it!
OK, after submitting via the "hey, you rejected me in error" link, I got another rejection email, but this one had the magic line "Crashes on ASUS Zenwatch".
Some googling led me to discover the Asus uses "Low-bit ambient mode". I then discovered in my Huawei developer options I can force that. Did so and hey presto- it crashes!
At least I have a stack trace now and can fix it.
I recently released my app to the Google Play community. The team and myself tested the app on Gingerbread, jellybean, and kitkat. All were either Samsungs or Nexus. Now we have someone getting a crash on a Motorolla Droid Bionic, Android version 4.1.2.
My app required wifi (not Cell data) connection which is not possible with androids emulator. I am in the process of installing android on VirtualBox but I don't know if this will allow me to identify the problem.
Should I be this concerned? This is my first app and I want to make sure it works for everyone? This app is for controlling a home appliance so I feel like we need to make sure that it works, but I'm not sure how to really get accurate test results and error messages.
What do other developers do to emulate accurately specific phones and OS versions?
thanks for any advise and help.
Ask for the "Stack Traces" reported in "Crashes & ANRs" section of your application in Google play Developer Console to have more details about the problem.
I've an app in the market with a few crash reports of "java.lang.RuntimeException: native typeface cannot be made". This is covered elsewhere on SO and I know where in my code it is. That's not my problem - the problem is finding out which Android version and handset type is causing it. I've never seen this on any handsets the app is tested on, nor does any version of Android on the emulators raise it. The only crash errors I see are these and always on "Platforms OTHER". I'm assuming if a different crash was reported I'd get a better clue regarding the platform - I'd expect to see "8", "11" etc.
It's a paid app. It happens right on first run so the users are cancelling the purchase.
Does anyone know what this platform is please?
In my experience, the developer console reports very few of the crashes occurring in your app.
If your app already requests internet permission you can use an error reporting library.
I use ACRA in my app. It's very easy to integrate and you'll be amazed at the number of crashes that don't get reported in the market developer console.
The Platforms section displays the device the crash occurs on, not API level. However, as you've seen, it's very limited. The only values I've seen besides OTHER are
T-Mobile myTouch 3G
Nexus One
Droid
Anything else is lumped in with OTHER. Obviously, the list of devices it separates out is vastly incomplete and not very helpful. Until Google improves it, the Platforms sections is essentially useless and I recommend using a third party library to get better information.