targetSdkVersion should be incremented to match the latest API level, then thoroughly test your application on the corresponding platform version.If the compileSdkVersion is higher than the version declared by your app's targetSdkVersion, the system may enable compatibility behaviors to ensure that your app continues to work the way you expect. If the device is running Android 5.1 (API level 22) or lower, or the app's targetSdkVersion is 22 or lower, the system asks the user to grant the permissions when the user installs the app. If the device is running Android 6.0 (API level 23) or higher, and the app's targetSdkVersion is 23 or higher, the app requests permissions from the user at run-time.That targetSdkVersion impacts the way in which permissions are requested:.I'd like to supplement those answers with the following notes: and there are several great answers above- essentially, that the compileSdkVersion is the version of the API the app is compiled against, while the targetSdkVersion indicates the version that the app was tested against. If you do not specify the targetSdkVersion, it defaults to the minSdkVersion. This will ensure your app looks as good as possible on the most recent Android devices. There are a few other known examples that are influenced by this value and that list is likely to only increase over time.įor all practical purposes, most apps are going to want to set targetSdkVersion to the latest released version of the API. The Android OS, at runtime, may change how your app is stylized or otherwise executed in the context of the OS based on this value. This is more like a certification or sign off you are giving the Android OS as a hint to how it should handle your app in terms of OS features.įor example, as the documentation states:įor example, setting this value to "11" or higher allows the system to apply a new default theme (Holo) to your app when running on Android 3.0 or higher. The targetSdkVersion is supposed to indicate that you have tested your app on (presumably up to and including) the version you specify. The targetSdkVersion has nothing to do with how your app is compiled or what APIs you can utilize. If you set compileSdkVersion to 16 you can still run the app on a API 15 device as long as your app's execution paths do not attempt to invoke any APIs specific to API 16. If you try and use API 16 features but set compileSdkVersion to 15, you will get a compilation error. This means you can use Android API features included in that version of the API (as well as all previous versions, obviously). The compileSdkVersion is the version of the API the app is compiled against.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |