YES, it's a) but you see, my app is not prepared to NOT be able to access files in its own app-private directory just because it has been updated. It's not like it's not prepared to SAVE something, but surely the app should not be prepared to not be able to read its settings.
Am I supposed to wrap ALL my code in exception handlers? What good if I do that? Display a message box to the user saying "Can't access own files. Tap OK to die."??? It's also an intermittent problem, and this has been said on all groups a googol times already. I've experienced it as well - I've released several updates to my (now removed) free/Lite version of the game (removed PRECISELY because of the f/c comments/bad ratings after an update) and get mixed comments - the users who don't experience force close issues say it's great, and a bunch of users say it force closes all the time on startup. You can imagine that after every update I'm the FIRST to update it on my G1 and surely I don't experience any issues, so I can't do ANYTHING to see what's wrong. Now let me tell you 1 other thing - I've *never* had a crash report for my game after it has been successfully updated and won't crash immediately on start up. The free game, before I removed it, had ~9K users, so I guess that's enough testers. None of them commented "I did that and the game crashed". Ever. However, I'm planning to add a catch-all logging and log stacktraces on unexpected crashes using a script on my website, so if I ever experience the FC issues again I can at least analyze them, and eventually file a bug. But in the meantime, you guys, who have never experienced that, and you don't know the quality of all applications on the Market better not come up with conclusions. "The platform is fine, I see a force close from Android Core once in a very great while" - are you KIDDING me? Cheers On Tue, Mar 24, 2009 at 2:28 AM, Eric Mill <[email protected]> wrote: > > It's (a), though they can be harder to completely catch in more > complex programs. The platform is fine, I see a force close from > Android Core once in a very great while, and I can live with that -- > it's not like I have to reboot when it happens. > > -- Eric > > On Mon, Mar 23, 2009 at 6:09 PM, Stoyan Damov <[email protected]> wrote: >> >> Frankly, I don't know whether to wish you to never experience the >> Force Close from hell after an application update, or to not >> experience it. >> But since you know so much about properly written programs and >> testing, I'm a bit leaning that you *do* experience it first hand with >> your paying customers. >> >> Cheers >> >> On Mon, Mar 23, 2009 at 11:49 PM, lbcoder <[email protected]> wrote: >>> >>> Force closes are caused by various unhandled exceptions. If the >>> program is properly written and tested, there will be very few (if >>> any) exceptions. >>> Don't let buggy applications trick you into believing that its an >>> unstable platform. I have never seen ANY mobile platform anywhere NEAR >>> as stable as android. >>> >>> On Mar 23, 2:16 pm, Streets Of Boston <[email protected]> wrote: >>>> Most (not all) force-closes can be avoided if your app is tested >>>> properly. Some apps are rushed out the door. This means that option a) >>>> is the most likely source of them, although 'devs' are not the >>>> problem. '*Some* devs' are the problem and don't test well enough. >>>> >>>> However, some of Android's behavior is not well documented and is >>>> discovered by accident --> that points to option e). Developers have >>>> not yet had the chance to discover all issues with Android and find >>>> ways to work-around them. >>>> >>>> About the 'Pictures' app. I've seen this as well. The insertImage >>>> method of the mediastore is not well behaved. If you don't run a >>>> MediaScanner sweep over a newly inserted image, you'll get this error. >>>> Maybe this is as designed, but not (well) documented. If you do an >>>> insertImage and later query this image, your results obtained from the >>>> Cursor returned by the 'query' are undefined (e.g. picture with size >>>> of 0 bytes, and such). >>>> >>>> The android.core force-close... I've seen this as well at times and it >>>> worries me a bit. I have no idea where this one comes from. >>>> >>>> On Mar 23, 1:50 pm, "[email protected]" >>>> >>>> <[email protected]> wrote: >>>> > Seeing them everywhere : >>>> > - downloaded apps, including paid. >>>> > - bug in the default picture viewer, which causes it to force close >>>> > if pictures are inserted into media library before a phone reset >>>> > - sometimes I see android.core force close when returning to my home >>>> > screen >>>> >>>> > Is this because : >>>> > a) devs are rushing out poor quality apps without testing >>>> > b) no two user phones are the same, hence devs can't predict what >>>> > exceptions they are going to see >>>> > c) devs need time to figure out the best ways to build for the >>>> > platform >>>> > d) the platform is inherently unstable >>>> > e) the platform is unstable right now, but time will iron out these >>>> > early issues >>>> >>>> > I'm hoping the answer is e - but I'm wondering what people think about >>>> > this. >>> > >>> >> >> > >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
