2012/4/20 Kostya Vasilyev <kmans...@gmail.com> > So, changing the targetSdk may break code in various ways and requires > careful (re)testing. >
Yes, the whole reason for targetSdkVersion is to allow the platform to turn off various compatibility behavior for older applications. If you bump up your SDK version, you are saying you have fully tested your app against that SDK version so are not relying on any of the older compatibility behavior. You can see many many things listed here that are impacted by SDK version: http://developer.android.com/reference/android/os/Build.VERSION_CODES.html Actually there are a number more that aren't spelled out so well in the current public doc (but are usually documented at the APIs that are impacted). I also recently in our development tree went through and tried to get in the documentation in VERSION_CODES everything that is impacted by targetSdkVersion. -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. 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
