Well crash reports are now handled natively, at least in froyo... I'd really dislike apps being able to launch activities after they've just crashed.. personally ill hit send bug report and wait for the next update notification before I try it again..
Users who moan about FCs will hopefully disappear when (if) they get upgraded to froyo.. Adding something like this could only be done on the next API release anyway.. so seems kinda redundant? Anyway - just my 2c! Kiall > I was thinking it might be useful if the platform let an activity > either programmatically or in the application manifest register an > intent that would be fired if the activity crashes due to an error, > force closes, etc. > > This could either launch a simpler help activity in the apk (which > might attempt to determine device type /version to report), or simply > launch the browser to go to the developer's support / bug report > page. Either way, it would be better than all the "force closes on x" > observations cluttering up market comments. (In neither case could > the intent exceed the permissions of the activity registering it) > > Yes, there are some possibilities to find things left behind on the > next run and realize a problem occurred - but a more built-in method > for getting users practically in touch with support would seem > beneficial. > > -- > You received this message because you are subscribed to the Google Groups "Android Discuss" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to [email protected]<android-discuss%[email protected]> . > For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en. > -- You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en.
