Hello Mike, Could you share how you implemented the bug report mechanism? How can you get a stack trace when the app crashes inside the UI thread?
Thanks On Sat, Apr 11, 2009 at 6:51 AM, Mike Hearn <[email protected]> wrote: > > I really question what developers are doing to get so many F/C > comments (and I see them on other apps all the time). > > I have a crash/bug reporter integrated into my app. It's not a very > good one - it just uploads exception stacktraces and some data to my > server when the core logic code crashes, so it doesn't even cover UI > bugs. > > I have hundreds of reports from the wild (about 25k downloads). So > obviously my app does fail. Yet, the comments on the app are all > glowing, and people are remarkably willing to give 4 or 5 stars even > when it didn't do quite what they wanted. I really wonder about the > buggyness of apps that get significant numbers of F/C comments. > > It must be frustrating to see comments about bugs that you can't > reproduce, but at the same time, I think some people here believe > writing software is easy. It's hard. I did all kinds of testing with > my app, including disrupting its network connection at various points > as it runs, repeatedly sliding the screen to force activity > reconstruction etc. Some bugs still slipped through, fortunately the > crash reports identify them quite well as most people with problems > will never even leave a comment, let alone email you to help you > figure out the problem. > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
