When an app crashes due to an uncaught exception, the user can submit a crash report, that shows up in the developer console, showing a stack trace and other useful information. But if the app catches the exception, it doesn't crash and I don't know of a good way of receiving diagnostic information about the exception. I suppose I could compose a report and either send it to a server somewhere or prompt the user to email it. But it would be really useful if the app could generate something like a crash report (without actually crashing) and have it reported through the developer console.
Similarly, we sometimes hear from a customer about an app behaving incorrectly (e.g., blank screen). Again, it would be nice to have a tool by which the customer could report the logcat output from the app (in case any exceptions were caught and logged, or simply to see the flow of activities). (As of Jelly Bean, third-party apps like CatLog cannot read my app's logcat output.) Ideally, the tool could be invoked at the system level (maybe through app management settings?) to submit a report through the developer console. The alternative is to start removing catch clauses so that the app will, in fact, crash and the developer can at least see something. This seems like a silly approach, though. Any suggestions for what to do about these situations? -- -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
