And to add insult to injury, the "View" item has disappeared from my Marketplace menu AGAIN.
I would be fired from my day job - QUICK - if my applications had such problems. On Mar 10, 9:26 am, Stoyan Damov <[email protected]> wrote: > Like I said, reproducing the bugs is hard, but these do occur and do > occur on a regular basis, as you probably saw on the forum. > We can't ask users to install adb and send us logs, wait, we don't > know who these users are thanks to Market (for the free apps at > least), they wouldn't send us e-mail but will instead put a 1 * > rating. > > BTW, you've probably seen a question on the forum for the biggest > Market WTF in history - users being able to rate apps BEFORE they even > download and have a chance to run and see them. Isn't this EASY enough > to reproduce and send to the appropriate developer? Ditto for the > inability to install a downloaded app (the hanging install). > > I understand you are responsible only for the download manager (wrt > this particular bug) but you can help us and give a chance to > Android's future by digging into your colleague's bugs as well. > > Cheers > > > > On Tue, Mar 10, 2009 at 5:14 PM, Jean-Baptiste Queru <[email protected]> wrote: > > > Unfortunately I didn't seem to find anything in there that would hint > > at which phase of the download (and therefore whose code) would cause > > problems. > > > It'd also be interesting to know whether other downloads that go > > through the download manager succeed while market downloads fail or > > hang (e.g. long-pressing an image in the browser and saving it to the > > SD card). > > > Any reproduction case that can send a log (i.e. output of adb > > bugreport) when such issues happen would be very helpful to try to > > diagnose things. > > > JBQ > > > On Tue, Mar 10, 2009 at 7:11 AM, Stoyan Damov <[email protected]> > > wrote: > > >> Hi JBQ, > > >> Take a look at [1] and [2]. > > >> [1]http://www.google.com/support/forum/p/Android+Market/thread?tid=40dc0... > >> [2]http://www.google.com/support/androidmarket/bin/search.py?hl=en&forum... > > >> So it appears there *are* men at Google! > > >> Thanks > > >> On Tue, Mar 10, 2009 at 3:56 PM, Jean-Baptiste Queru <[email protected]> > >> wrote: > > >>> In cases of hanging "downloads", do you know whether the users are > >>> seeing an actual download icon in the notification bar (it looks like > >>> an arrow pointing down)? > > >>> Longer explanation: There are two phases in a "download", one where > >>> the Market uses its own protocols to retrieve the download URI, and > >>> one where the Market instructs my code, the Android Download Manager, > >>> to get the actual bits using the Android HTTP stack. My code displays > >>> the download icon, and whether that icon is present or not is a good > >>> hint to know whether the problem is with Market retrieving the > >>> download URI or whether it's in my code failing to download the data > >>> (which could also technically be an issue with the underlying network > >>> stack, though that should be rare). > > >>> JBQ > > >>> On Tue, Mar 10, 2009 at 6:45 AM, Stoyan Damov <[email protected]> > >>> wrote: > > >>>> Hi Android engineers, > > >>>> It's been weeks since we, developers, and many users, started ranting > >>>> about the bugs in the Android Market application, namely: > > >>>> 1. Hanging downloads > >>>> 2. Hanging installs > >>>> 3. The DREADED "Force Close" after an application update. > > >>>> Many of us have received low ratings (especially 1 star ratings) > >>>> because of the aforementioned issues. > >>>> I took the time to review more than 100 applications, all in different > >>>> categories, and most of them sacrificed some of the RIDICULOUS 325 > >>>> characters[1] description in explaining to users that 1, 2, and 3 are > >>>> actually not their fault but yours (Google's), and setting up websites > >>>> for alternative downloads. > > >>>> All of the problems above are intermittent and are thus hard to > >>>> reproduce and we understand that. > >>>> What we don't understand is how much more will we have to listen to > >>>> the sound of silence. > >>>> Is there an Android engineer, man enough (or woman enough) to stand up > >>>> and say *anything* about these issues, whether they are acknowledged, > >>>> or being reviewed, or someone is working on them, or whether and when > >>>> there's a planned deadline on fixing any of them? Also, is Google > >>>> going to stand up and say "we fucked up, it wasn't the devs fault, but > >>>> now everything's back to normal, sorry for the inconvenience" > > >>>> So far, it appears that you are HIDING, and I can't stress enough how > >>>> much I hope that's not true, and that the reason for the silence is > >>>> that you're actually extremely busy busting your @$$3$ working on > >>>> fixes. > > >>>> Thanks > > >>> -- > >>> Jean-Baptiste M. "JBQ" Queru > >>> Android Engineer, Google. > > >>> Questions sent directly to me that have no reason for being private > >>> will likely get ignored or forwarded to a public forum with no further > >>> warning. > > > -- > > Jean-Baptiste M. "JBQ" Queru > > Android Engineer, Google. > > > Questions sent directly to me that have no reason for being private > > will likely get ignored or forwarded to a public forum with no further > > warning.- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
