I think it would be a great help for the developers to create an Automated Crash Report System for published applications.
When an application crashes, and the message dialog pops up with the famous "Force Close" button, there could be one another button with text: "Send Report", like in other applications, we saw before (for example: FireFox), and when the user presses the "Send Report" button, the system would open up the default mail application, and would precompose a message to the author of the application, with subject: ANDROID CRASH REPORT - <package.name> - Device Type. The body of the e-mail would be the Exception's stack trace, or a more detailed log about the current activities, like the one, which the third party SendLog creates. Most user won't click on the "Send Report" button, but if some do, they still have the control over if they want to send the report or not, and what does it contains actually about their phone's state. Naturally this Automated Crash Report System could only help in the most fatal cases. For testing on actual devices I would prefer a subscription based Device Anywhere kind of service. L On jan. 19, 09:32, String <[email protected]> wrote: > Problem is, half the time we don't know. Users post 1* Market comments > saying "Force closes on Droid" or "Doesn't work on Samsung Moment", > and unless you have that specific handset to test on, you're SOL. You > "sanity check" on an emulator instance of the same resolution and OS > version, and nothing is obviously broken, so where do you go?
-- 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
