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.
Related
I wanted to know if any one who is experienced with both App Store Connect & Google Play Developer Console what is the difference in the crash reporting logs it shows vs if you use say for instance firebase crash reporting(crashlytics) ? Is there any major difference ? I’m asking because I’m deciding if I should integrate firebase crash reporting in my app or if the crash logs it shows on the developer consoles (iOS&Android) would do the job?
The crash reports in the app stores are very minimal as far as features go. Using something like crashlytics or any other analytics suite has much more tools and data points as well as other metrics that simply don't get reported in the app store reports.
Unfortunately the GooglePlay Console and Crashlytics report different ANRs/crashes.
Status today, July 27th 2022 taking one of my apps as an example:
the Play Console reports 4 crashes over the last 30 days. None of the 4 are visible on Crashlytics.
on the other hand Crashlytics reports 2 ANRs and 1 crash over the last 30 days. Again these 3 incidents are not visible on the Play Store Console.
Conclusion: I'm afraid you will need both - and probably still won't be able to fully trust the reports
I just received reports from some of my users who's running Lollipop, they're saying that my app would crash (with the message: App Stop Working) if they tried to launch it by clicking on my app's icon on their home screen. But if they launch my app from Google Play Store, the app would work without any problem.
What could be the cause of this? If it's any help, here's my app https://play.google.com/store/apps/details?id=com.imincode.meniti
Btw there's no mention of any Crashes/ANR in my Google Play Developer Console.
The issue is you need to get the stack trace. Google Developer console is not sufficient in tracking bugs in your app. It misses the vast majority of in app crashes. I think there are a few options here.
1) I would try replicating this with the emulator and see if you can get the stack trace there.
2) I would embed a high quality crash tracking library in your application to be able to better handle this in the future. Currently I would recommend using Crashlytics. In my opinion they have the best crash reporting library on the market today. ACRA was very good several years ago before professional products came out, but does not hold up compared to modern trackers like Crashlytics.
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.
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