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 -~----------~----~----~----~------~----~------~--~---
