If you are not using reflection or not trying to use any non android.* API or non android.R.* resource, then a compatibility check would not help. The SDK *is* the compatibility check (except, unfortunately for the case discussed in this thread before.)
On Tue, Feb 17, 2009 at 1:58 AM, blindfold <seeingwithso...@gmail.com> wrote: > > I'd welcome that too. For some reason my app's Listview-based menu > according to recent user reports breaks (crashes) on some phones, but > I cannot get it to break on my vanilla dev phone 1 (thus making it > very hard to track down and fix the problem). I'm not using any > private classes AFAIK, but any supplemental compliance checking for > proper usage of APIs could prove helpful in reducing the chances of > inadvertently running into firmware dependencies. > > Thanks > > On Feb 8, 11:10 am, Al Sutton <a...@funkyandroid.com> wrote: >> Looks like we're on the same page :). >> >> Just PLEASE make this a public API checker (possibly as part of the >> SDK). I'd happily include the check into AndAppStore, and I'm sure Shane >> would be interested in putting into SlideME as well. >> >> Al. > > > > -- Romain Guy Android framework engineer romain...@android.com Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
