Hi guys, Thanks for your informative comments and discussion. In "Android, send me logs!", I am just taking the simplest possible approach - sending logs by email looks like the simplest and most reliable way and best understood by users.
Of course, the anonymity of users might be an issue. But it can be resolved by sending a POST request to a given URL. That requires some extra coding in the host client, for example to render a UI for users to review the content being submitted, UI and error handling code for submitting the POST request etc. I'm planning to build this into the next release if you guys don't mind. :) Compared to the defaultUncaughtExceptionHandler approach, analyzing logs has some advantages: - it's capable of capturing extra errors such as another infamous WNR (Window not responding) error, and even VM crashes due to Android bugs - it looks like a simpler approach to me: it doesn't interfere with existing code, whereas using defaultUncaughtExceptionHandler you would need to carefully relay to the default handler of the system, and like "Streets of Boston" said, you probably need to deal with extra stuff such as services; Of course, since the logs are not part of Android's official API, the result might be unreliable if not implemented correctly. But by analyzing existing platforms and applying some heuristics, I believe the result would be good enough for the majority of applications. BTW: What "laphroaig15" mentioned about connecting the submitted logs to bug tracking systems sounds like a good idea. Maybe there could be a system on the server to remove/group duplicated bug reports/ submitted logs? Keep looking forward to more of your feedback. Linton -- 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
