Not sure if this is meaningful statistics .... I have received 1 person reporting that my app doesn't work after updating. He tried uninstalling and reinstalling and the app still doesn't work.
This is 1 out of about 10,000 people who downloaded my app. I have pushed about 15 updates in 8 weeks so I assumed there have been at least 10,000 attempts of updating. To me, 0.01% is certainly not widespread. But again, if Google could fix this I certainly wouldn't mind :-) On Thu, Apr 9, 2009 at 8:22 PM, Incognito <[email protected]> wrote: > > > Hahahaha. Pretty funny. It most feel like people throwing stones at you and > the e-mail below is just the involuntary reflex to raise your hands to > shield yourself. > > On Apr 9, 2009, at 8:09 PM, Mark Murphy <[email protected]> wrote: > > > Stoyan Damov wrote: > Especially when > Google are so strongly supported by so many zealots who think Google > devs can't make bugs and it's all the developers' fault. > > Since I suspect that's aimed in my general direction, let me be clear: > > Google developers can "make bugs". Considering how many they have > pointed out on these lists, I suspect they'd be the first to tell you > that they "make bugs". > > You have reported several bugs on these lists. As I recall, for these, > you indicated, in no uncertain terms, that if they affected you, they > must affect everyone, and that they are clearly bugs in Android proper > with no other possible cause. > > I don't recall in any of those situations questioning whether the > symptoms were real. I asked for more evidence on the claims that they > affect everyone, that they were unequivocally bugs in Android proper, > plus for ways to reproduce the problems. The latter is the most > important, because no matter how the symptoms are caused, without > reproducible scenarios, fixing them is well nigh impossible. > > In some cases (e.g., force-close-after-update), such evidence has > arrived, at least on the first two points. If we're lucky, the same > thing that causes this problem is what causes the similar force-close > triggered by changes to the AndroidManifest.xml file, that somebody > reported, I reproduced, and I opened an issue for. I doubt they're the > same thing, but one can only hope, since reproducing > force-close-after-update is obviously difficult. > > In some cases (e.g., "TERRIBLE BUG"), evidence definitely points to a > bug in the build tools, though no evidence has arrived that indicates it > is currently affecting every Android developer. And, IIRC, we still > don't have a reproducible test case. > > In some cases (e.g., takes-15-seconds-to-pick-up), we have neither > evidence of a widespread phenomenon nor conclusive evidence of a purely > OS problem. In this specific case, I'm still backing my theory that it's > out-of-spec hardware that is reacting poorly with a new driver in RC33. > Heck, if I were HTC, I'd buy your phone off of you, just to have a > sample of the problem on hand. Alas, I am not HTC, nor do I play HTC on TV. > > If I'm a zealot for asking for evidence to back up sweeping claims and > broad generalizations, and for hoping for more civil discourse than > sometimes is seen on these lists, then I'm comfortable with that. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://twitter.com/commonsguy > > Android App Developer Books: http://commonsware.com/books.html > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
