The best solution is to set it to 9 and then test your app on a 1.6 device
(or a 1.6 emulator if you must). You can also use reflection for any new
features that would throw 1.6 into a wobbly.
--
You received this message because you are subscribed to the Google
Groups Android Developers
Yeah know about the reflection solutions.
But can't find anywhere a clear explanation on what happens with XML
tags you use that are available in newer SDK versions (as set in your
targetSDKVersion), but not in your minSdkVersion... Are they just
skipped by the older versions?
On 10 apr, 13:23,
yes, they are ignored by older versions
--
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
Whenever we talk about changes in behavior for compatibility, we are talking
about targetSdkVersion. The targetSdkVersion you set is the highest version
you have tested your app on, so the platform assumes you don't need any of
the compatibility features for applications developed against older
4 matches
Mail list logo
