Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
since the latest version of my Android application I got some bug reports (via email) that my application doesn’t work anymore. It does not crash but doesn’t work anymore. Only a few users (<0.05%) have this problem. I don’t see any similarities (same phone/provider/…).
Has anyone an idea how I can tackle this problem and find the bug?
If I publish a debug version of the application, is there any tool that the end-user can use to grab the logcat output and send it per email or…
Thanks!
My suggestion is that you incorporate a logging feature on your app, even the retail one. Make a log of critical/fatal errors, but try to minimize the log size (e.g. erasing it periodically or only logging really really critical errors). This way you can request such logs for such users, without having them install a new version of the app, and having them to recreate the erros, since sometimes recreating the whole situation in which such crashes occur is close to impossible, or that it doesn’t happen for some other reason in a debug version.
You can also incorporate a function that sends you the log periodically, or just request it to the users.
I don’t know any tool other than ADK to grab the logcat…