On Sat, Nov 12, 2011 at 1:02 PM, Binxalot <[email protected]> wrote: > Does anyone here have a way they catch these types of force close > issues that don't result in a "send feedback" screen being shown?
Sure. Catch the exception. Typically, for unhandled exceptions, you use Thread and setDefaultUncaughtExceptionHandler(). Then, take a look at solutions like ACRA for capturing and collection the stack trace and related data. > I know some of you are going to say don't put out buggy apps (and we > do test constantly) but anyone who's been doing this for a while knows > that you can't support all phones and devices, especially if they are > new model phones just released, its impossible, especially when you > add in customers that have rooted phones with memory managers on them, > when you add that in its almost like developing for windows 95 all > over again. Then only distribute to devices that you have tested it on. Or, add in some amount of analytics to see what devices you are currently supporting successfully, and distribute to them as well. Plus ensure you have all the right <uses-feature>, <uses-configuration>, and <compatible-screens> elements in the manifest. You can filter devices via the Developer Console for the Market. Then, start using solutions like apkudo, TestDroid Cloud, and LessPainful to extend your testing to more devices. Or, borrow devices at local GTUG/Android Developer Group meetings. Those that seem to work OK you can add back into your distribution. Eventually, once you get enough devices that you are comfortable with, across a range of screen sizes/densities and other configurations/features/versions of relevance, you might consider lifting your device exclusions and distributing to all devices again, addressing problems only as they arise. It is not "impossible" to "support all phones and devices, especially if they are new model phones just released". However, it is probably more difficult for games and other apps that push the envelope on device capabilities. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training...At Your Office: http://commonsware.com/training -- You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en
