I posted a free app and I've got a couple users who posted a comment saying that the app force closes in google's feedback. It's got a few hundred downloads in the day it's been up with an 84% retention rate. Google's error report in the developer's console says it has 0 errors. I've never had an app that reported any errors in the console. Does it actually work or am I getting fake reports of force closes? I'm a bit suspicious competitors might be posting the comments, but I don't have any way to confirm that the error reporting google provides does actually work.
As far as I know, the 'Report' button is only available on devices running FroYo (2.2) or later, which is very few.
At least I've never seen the ability to report an error upon force close.
I don't think there's any reason to assume your users are lying to you. But it's always a good idea to include something in your app that'll allow for the users to submit an error from within the application.
http://groups.google.com/group/android-developers/browse_thread/thread/ddf6863e9a31052f?pli=1
you could use this project http://code.google.com/p/android-remote-stacktrace/ to verify
Related
So I have used App Actions in my app for a couple of years, last week I pushed a maintenence update that has been rejected by Google. After some to and fro with Google Play support, the best I have managed to get out of them for the reason is "App Actions", and I should read the program requirements (the link they sent me has no program requirements section).
It's odd, as I have changed nothing in my app-actions area of code for a very long time, so I can only assume Google have quietly tightened some rules, and my app is no longer complaint. Unfortunately, my crystal ball is currently away for cleaning, so unable to use it, I'm hoping someone else might have some real-world specific examples of how an app may not be compliant in the area of app-actions.
Thanks.
Unfortunately, there are no straightforward rules specified by Google, so you have to go with some trial and error here to see what red flag(s) is your app raising. You can check this article to see all the potential reasons on why Google may reject your app.
I am getting stability alerts that my app is now going under 67% crash free users so of course I got scared:
I went to Fabric to check what was happening and I see absolutely no crashes:
I also checked Firebase since I migrated the project, and nothing shows up there either.
What might be going on here?
As a follow up,
The developer wrote in to support at fabric(at)support(dot)io and was able to have this issue resolved. The cause was an API key error, which caused reports to not be sent to the developers Fabric Dashboard.
I have been testing my application with my relatives through distribution via Google Play's alpha testing feature. Crashes have been showing under "Crashes & ANRS" for a while. However, there have been many crashes in the past few days but none have shown up on this page at all. I have spoken with them and they have assured me that there have been crashes and that they have been reporting them and sending them off to Google.
Does anyone know why the Crashes & ANRS page on the Google Play Developer Console doesn't pick up these crash reports anymore? I haven't contacted Google about this yet but I will do so now as well.
edit:
Okay so I just checked today and all of the crash reports have just shown up. I guess it can take up to a day or so for the reports to show up.
It was just a case of not being patient enough.
Okay so I just checked today and all of the crash reports have just shown up. I guess it can take up to a day or so for the reports to show up.
It was just a case of not being patient enough.
I can recommend you use Crittercism. Then you will have actionable crash reports immediately, both in release and during development if you so wish.
You can also know with some confidence whether your app is actually stable or not, and prioritise what you need to fix.
So, there are two points here:
1) It depends on the user's decision to 'Send Report' (or not) on any crash perceived during app usage. To check all of the stack traces generated by your application, you must implement third-party crash reporter or start testing Firebase Crash Reporting (https://firebase.google.com/docs/crash).
2) In my experience using the Google Play console, a reported crash/ANR may take some hours to reach your dashboard.
I have been working on an android project and published it to the market. I then installed the app on my device via the play store and upon doing something I found a possible way to crash the app.
When the app force closed it asked me if I wanted to send a report which I did so I could see what it looks like in the developer console.
I added some text about what I did to cause the app to force close and could then view what the crash report looked like and it conained various information like device make and model etc. I submitted and I logged in to my developer account but could not see any of the information within the crash report other than the message I put inside explaining what I did.
Where does the rest of the information go as unless someone actually says what phone or android version they are running in the message I don't what I need to replicate the issue.
Thanks for any help you can provide.
AFAIK, you cannot view the device etc. in the developer console. You can only view the user message (if provided) or the stack trace. Beyond that there is no more information as far as I know.
However, you can get much more information by integrating ACRA into your application. This will give you a huge amount of information about the crash, including memory statistics, the device, the android version it is running etc.
EDIT
It would seem that the device at least is displayed in the new Developer Console, but the information still isn't even close to what ACRA provides.
With the standard report included it depends a bit on android(?) or play store app version what details you get in your reports it seems. In the publisher/developer console (example from the new developer console version):
I have an App available in the Android Market.
From time to time i get error reports in the Developer Console. For about 6 month there have been no more stack-traces visible. At first I though no more post-froyo bugs: 'yay'!
Recently I did some testing using a droid 2 which I am sure is not pre-froyo, I ran into an error, reported it, and never received this report in the Console.
Did I miss some configuration or option that enables me to receive stacktraces?
Is there something I can do about it?
I have no idea why you don't receive stack traces anymore nor how could you enable them. I have always felt Android Market is a somewhat unreliable service: reports are not accurate, downloads/active counts randomly change at times, crash reports not received, and so on.
However, I have suggestions how to implement similar functionality yourself and with a more reliable fashion: How do I obtain crash-data from my Android application?
Basically there are two options:
Use an existing component (like acra)
DIY by catching all uncaught exceptions.
(So you would have an option should you fail to receive a real solution)
I'd suggest you to stop listening to android market and work with other tools.
You should consider using a crash report tool like http://www.bugsense.com/ which is simple effective and meaningful
NOTE: i am not linked nor affiliated in any way with bugsense owners. I am just a simple user.