Forgive if I have this wrong, but I thought the report button only shows for Froyo and beyond. I certainly don't see it on 2.1 on my GalaxyS.
If its for reporting the crash to oneself (as it seems to be - to handle all Android versions), then handing it off to another process to send the data to a remote site seems to be a practical solution, rather than relying on a process that is already in a bad state and is trying to destroy itself. That way the process that is responsible for sending the crash info can handle all the flows associated with a remote connection without being constrained by immediate destruction or UI responsiveness. On Nov 10, 7:29 pm, Dianne Hackborn <[email protected]> wrote: > On Wed, Nov 10, 2010 at 1:25 AM, William Ferguson <william.ferguson.au@ > > gmail.com> wrote: > > Um, I think the point that Lance was trying to make was that he won't > > actually know about the force close UNLESS he uses the remote service. > > But sure, once he knows about, then he could fix it. > > If the user hits the report button, the crash information will be available > through market feedback. > > If you are just catching the error to report it yourself, there wouldn't be > a crash dialog, so no button for the user to press to kill the app before > you are done. > > -- > Dianne Hackborn > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. -- 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
