>>No, most are NOT. People, for @#$%'s sake, you've GOT to trust me on that. I've downloaded an e-book the other day. I read it (it's a short story), and the next day I got an update. I installed it curious to see what was updated (was the reader itself). I ran it. It crashed IMMEDIATELY after launch before showing any UI. I then uninstalled it, and re-installed it, and it started and worked flawlessly.
I'm betting my ass that when Android updates an application it @#$%s up something, e.g. permissions (damn me for NOT launching Eclipse when this happened to see what exactly was the crash) and the app would F/C. After a reinstall, everything works just fine.<< I have to say that your logic is seriously flawed and you shouldn't bet any parts of your body on it that you feel fond of. If re-installing the FB reader made it work, it doesn't say anything about the upgrade at all. This can be a totally different code path. Just a quick story: After my latest release I got one of those fantastic comments: "Doesn't work, forced close" .. or something beautiful and helpful like that. I thought that couldn't be possible because before releasing the app in the market I test it as an upgrade from the old version and then from a fresh install. Also I have an automatic error reporter that opens an email to me when an exception occurs. So I went ahead and did the usual jumbo of figuring out if the user name can be mapped to any real person. I was lucky and contacted the poster. Even thought the procedure of commenting, but not contacting me is questionable, he was very nice helping me out. He had Log Collector installed and send me the log file. I fixed the bug, uploaded a new version and all was well. So, what was it? I write stuff to an SD card or to phone memory. The user can select that. The default is set when the app is first launched. It is set to SD card when it is accessible in r/w mode and to phone memory when the SD card is not advisable. In my method "isAdvisable()" I check if the SD card is mounted, r/w and then check how much space is left on it. For this I tried the directory that I write stuff into (/sdcard/mydir). This directory was always there on my device as I am not notified when my app is uninstalled and so can't really clean up after me. But this lead to the code working with a fresh install and from an update, but not for first time users that haven't got that directory on their SD card yet. My Bug reporter didn't open because it includes information about the used file system, and I didn't catch errors when querying it. So the bug was unlikely (or so I thought), but just as well my fault. On Thu, Apr 9, 2009 at 11:20 PM, Stoyan Damov <[email protected]>wrote: > > No, most are NOT. People, for @#$%'s sake, you've GOT to trust me on > that. I've downloaded an e-book the other day. I read it (it's a short > story), and the next day I got an update. I installed it curious to > see what was updated (was the reader itself). I ran it. It crashed > IMMEDIATELY after launch before showing any UI. I then uninstalled it, > and re-installed it, and it started and worked flawlessly. > > I'm betting my ass that when Android updates an application it @#$%s > up something, e.g. permissions (damn me for NOT launching Eclipse when > this happened to see what exactly was the crash) and the app would > F/C. After a reinstall, everything works just fine. > > What I described is what can be seen on MANY (and list is growing) > number of applications' descriptions on Android Market (that is > "please, uninstall before update"). > > I *do* believe people make bugs (and so do I), and that there are some > very poorly developed apps on Market, but this *particular* crash > immediately after an update is a Google bug. I know it. I KNOW it. I > @#$%ING KNOW IT! > > I'm just waiting for it to happen again with another app, and me > having Eclipse around. > > Cheers > > On Thu, Apr 9, 2009 at 6:50 AM, Mattaku Betsujin > <[email protected]> wrote: > > I think a lot of the comments are junk. However, I think the Force Close > > ones are real. On Android, the foreground app shouldn't be FC'ed if there > > are lots of background activities. > > > > On Wed, Apr 8, 2009 at 9:52 AM, Ivan Soto <[email protected]> wrote: > >> > >> We really need something like 'Report abuse" or "Inaccurate" > >> I try a lot of applications that run perfectly but I bet some people > with > >> a lot of background applications running will obviously have problems > with > >> the Force Close thing, they usually just go to the market and give 1star > for > >> that. > >> I would love to report that as inaccurate, because that is just not > spam. > >> Ivan Soto Fernandez > >> Web Developer > >> http://ivansotof.com > >> > >> > >> > >> On Wed, Apr 8, 2009 at 10:03 AM, Eric Mill <[email protected]> > wrote: > >>> > >>> I've written on this list a couple times about the deplorable state of > >>> Android Market comment threads. It has gotten better than it used to > >>> be, though, I think the "Report as Spam" option has made an impact. > >>> > >>> You're not going to get people to change the way they express > >>> themselves about how they feel about your app, though. YouTube has > >>> played with their comment system numerous times, but the comment > >>> threads are still a gutter. It's just the audience and the culture. > >>> Blocking out basic curse words just goads people to get around the > >>> filter. > >>> > >>> Like I said though, I think it's improved, I'm not seeing the same > >>> level of vindictiveness and bile that was there in the winter. It's > >>> just going to take some more time, and it's going to have to come from > >>> the community. > >>> > >>> -- Eric > >>> > >>> On Wed, Apr 8, 2009 at 10:47 AM, Ivan Soto <[email protected]> > wrote: > >>> > And yet no word from Google. Although, I can say that I've seen some > >>> > kind of > >>> > moderation. (I guess) > >>> > I haven't seen a lot of comments like > >>> > "your app rocks. 5 starss... contact me [email protected]" > >>> > Which was a big issue before. Still, it needs a lot of improvement. > >>> > > >>> > > >>> > Ivan Soto Fernandez > >>> > Web Developer > >>> > http://ivansotof.com > >>> > > >>> > > >>> > On Wed, Apr 8, 2009 at 8:40 AM, Sean Hodges > >>> > <[email protected]> > >>> > wrote: > >>> >> > >>> >> From my experience, auto filters have limited effectiveness, though > >>> >> definitely better than nothing at all. > >>> >> > >>> >> Ideally, there would be a "Report Abuse" button that acts similar to > >>> >> the spam feature, and in both cases if a Google account is reported > a > >>> >> number of times it is reviewed by market support for inappropriate > >>> >> activity (I'm not sure if this is already the case for the spam > >>> >> feature). > >>> >> > >>> >> If a malicious user starts picking on another by reporting all their > >>> >> comments, the data from this can be used to review the reporter's > >>> >> account instead... People abusing the system should get a warning > >>> >> followed by a ban on the market, or some similar course of action. > >>> >> > >>> >> Of course, if this is too much to implement, an auto-filter should > >>> >> definitely be considered as an alternative. There are lots of > reports > >>> >> requesting this in the market forum. > >>> >> > >>> >> > >>> >> > >>> >> On Wed, Apr 8, 2009 at 3:29 PM, [email protected] > >>> >> <[email protected]> wrote: > >>> >> > > >>> >> > Completely agree. I'm amazed there isn't an auto-filter going on - > >>> >> > it > >>> >> > would be easy to catch obvious swear words like the ones you quote > >>> >> > above. > >>> >> > > >>> >> > When I've seen abusive comments, the poster usually tries to > >>> >> > disguise > >>> >> > the swear words by changing a letter or by using asterisks > instead, > >>> >> > because of fear of being moderated I guess. > >>> >> > > >>> >> > But it looks like the moderating is not happening at all. > >>> >> > > >>> >> > > >>> >> > > >>> >> > On Apr 8, 2:48 pm, mask <[email protected]> wrote: > >>> >> >> This is an excerpt from an application comment: > >>> >> >> > >>> >> >> "This stupid fucking shit isn't downloading/installing! What a > >>> >> >> waste > >>> >> >> sherelle 2009-04-08 04:00:44" > >>> >> >> > >>> >> >> As a developer, I would like to know when is Google going to > start > >>> >> >> moderating such illiterate and ignorant people from commenting on > >>> >> >> an > >>> >> >> issue developer has no control. At least, the curse words should > be > >>> >> >> removed or 'moderated' for keeping the developer community sane. > >>> >> >> Keep > >>> >> >> in mind, in the long run its the developers and their application > >>> >> >> that > >>> >> >> will eventually sell and market android platform. > >>> >> >> > >>> >> >> As a developer, all ignorant and abusive comments are least > >>> >> >> productive. Also Google's inaction in removing abusive comments > are > >>> >> >> totally unacceptable. > >>> >> >> > >>> >> >> As a developer, I request Google to take immediate action by > >>> >> >> removing > >>> >> >> comments which are abusive or totally remove commenting but keep > >>> >> >> the > >>> >> >> star rating until Google provides a complete solution. > >>> >> > > > >>> >> > > >>> >> > >>> >> > >>> > > >>> > > >>> > > > >>> > > >>> > >>> > >> > >> > >> > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
