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):
Related
This is an information question rather than a technical question. I have an app in Google Market. I need to know stracktrace of errors happens in other phones.
I have investigated but I have not seen anything about it. Does anyone know if Google offers some service to look at the errors that your application is giving in the market and thus to be able to reproduce it?
Thanks in advance!
Well google offers one really powerful tool "Firebase" it provides great analytics and crash reporting. In addition to analytics and crashes it provides others utilities like Cloud-Testing, Push Notifications and many others.
Other popular solution is Crashlytics offered by twitter.
Open your app at the developer console and select "disruptions and ANR". Here you can select on of disruptions you have, then you can see error stack trace!
Or you can use appmetrica from yandex. Link to yandex.metrica It's very simple to integrate yandex.metrica to your app and get all data about crashes and statistic (country, city, android version and so on).
Link to console
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 want to add a Bug Report/Report Problem option to my app, which sends device and app info and a user's comment to the developer. I was wondering if there are any "standard" things to report? I am reporting OS Version, Device Name and App Version. Is there anything important I'm missing out and should include? What are you guys normally including ?
You could avoid sending out this data manually by integrating with a service like Instabug
which allows the user to report bugs through your preferred method, but mainly through shaking the device.
It will display a screenshot of the current view that the user can draw on for visual bug identification. What gets reported along is (but not only) the following:
App version
Device type
OS version
Location
CPU load
Memory usage
Storage
Connectivity
Battery
Orientation
Network and console logs
Visual reproduction steps
UI view hierarchy inspection
users can further describe the bug using text, extra screenshots, voice notes, or screen recordings.
All reports arrive in your Instabug dashboard containing various details such as:
Network and console logs
Complete Device details
Reproduction steps
Crash stack trace (In case of a crash report)
It only takes a line of code to integrate.
For full disclosure, I work at Instabug. Let me know if I can help.
Check out the free service
http://www.crashlytics.com/
you can get the features what is mentioned above.
I am new to android development and presently writting a small android application for the android market.
I would like to resolve application bugs when end users face them..
So, What is the best way to be able to collect issues from the end user of the application.
Should i store logs of my app to a file on the SD card ? and then somehow provide an interface in the app to send me that log by email ?
Or is there any already placed mechanism in android to facilitate this ?
Currently I have statements like
Log.i (TAG, "Message..");
and
Assert.assertNotNull(strSomething);'
Also please advise if they would go in the deployed code ??
Essentially what I would like to get to be able to fix issues is a stack trace of crash (if any) and any log file with my app messages..
Please advise...
Thanks
For user's running Android 2.2+ with the Android Market (Google Play) installed, they will be prompted to "Report" errors if an uncaught Exception or other problem occurs. You'll be able to view these error reports in your Android Market developer account.
You'll also be able to view statistics on what types of devices your application is installed on.
There are 3rd party services that offer more fully-featured error reporting, but I've found the built-in tools to be more than adequate.
If you find and fix a bug, you can release a new application version via the Android Market and your user's will be prompted to upgrade.
How do you instruct users to report a bug in Android? Any advice or tips?
I'd like to get send detailed instructions to my users to get the most of their bug report. I know there are various apps that send bug reports from the device and I was wondering how other Android developers deal with this.
A bug reporting SDK such as Instabug can let you achieve that.
As you can see, it displays, by default, a welcome message to your users 10 seconds after opening the app. It displays instructions on how to invoke Instabug depending on the invocation method you're using (A button or a shake gesture).
After signing up and including the library in your code, you can switch between different display messages. Use either of the following lines depending on whether you're in beta or production.
Instabug.setWelcomeMessageState(WelcomeMessage.State.BETA);
Instabug.setWelcomeMessageState(WelcomeMessage.State.LIVE);
Each bug report contains various information about device details, network logs, console logs, view hierarchy inspection, and visual reproduction steps.
For full disclosure, I work at Instabug. Let me know if I can help.
There are solutions for instrumenting the application in a way that will collect contextual information and allow the user to provide in-app feedback. Either by shaking the phone or some other trigger like a menu option.
Here is a "currently free" offering from IBM called Mobile Quality Assurance, that will instrument the application so that as a user uses the application contextual information is collected as they use the app. When they want to provide feedback or submit a bug, they can shake the phone and it will capture the screen at the time, give them a form to enter additional information and then submit the screenshot, contextual information and comments to the testing portal.
Here's a link for more info on MQA
Taking Gilbert's advice into account, I decided to create my own app. I hereby present you: Bug Reporter.
It allows users to send you a report with device information and optional logcat. It also supports intent extras to customize its behavior if case you want to launch it from your app.
You can do what google does with their new maps application on iPhone. When you're using the app and shake the phone (which users do when they're frustrated or something isn't working) you can pop up a screen that asks if something is wrong and is a form for bug submission that they can choose to fill out.
This isn't Android specific, but you could have a bug reporting screen in your application that sends the information your customers type, along with any system information you wish to capture, to your web server. Alternatively, the application could email you with the information.
There are some libraries you can integrate to do this job, you don't need to develop a solution yourself. For example, I'm using blit feedback. With this library you can take snapshots, draw on them and add some comments. I've configured it to send reports by email, but if you have an issue tracker you can connect it too.
Discovered this question a lot late. There are answers given but the products mentioned or the techniques are quite old now. Adding the tool that we have been working on - Bugclipper
This tool let's your users report issues from with-in the app Android or iOS and you can add/annotate screenshots, create screen recordings with voice and also get the crash logs.
p.s. - I am one of the co-founders.