In Windows, when an application crashes because of an unhandled exception, there is a place called Event Viewer
that gives a good amount of informative data about the process being crashed down.
Using that information, one can easily troubleshoot the application.
In Android, we have developed an application that on the phone of a customer keeps crashing repeatedly and we don't have a chance to log anything.
Do we have something similar here in Android? Or in general, how should we know about unhandled exceptions in Android?
Please note that because the app is installed on customer's phone, it's a user question. We want to know a way to be able to find a log somewhere somehow by the help of our customer, and act accordingly.
logcat
inadb
or the terminal in order to access the internal log. Keep in mind that this log can contain private information. For an application, you are better of using ready solutions like Fabric/Crashlytics, that register a handler for unhandled exceptions. – GiantTree Dec 04 '15 at 13:41adb logcat
(but notlogcat
in terminal) :) – Izzy Dec 04 '15 at 15:43adbd
(the process on the phone itself) is a system process, I forgot. Yes, that works. Otherwiselogcat
only returns the log of the own process/app. – GiantTree Dec 04 '15 at 15:44adb
is for when I'm developing and it's my device. We want to know how can we help our users access their phone log somehow and send it to us. – Saeed Neamati Dec 04 '15 at 16:27