<uses-permission>

Note: In some cases, the permissions that you request through <uses-permission> can affect how Google Play filters your application. If you request a hardware-related permission, such as CAMERA, Google Play assumes that your application requires the underlying hardware feature and filters the application from devices that don't offer it.

To control filtering, always explicitly declare hardware features in <uses-feature> elements, rather than relying on Google Play to "discover" the requirements in <uses-permission> elements. Then, if you want to disable filtering for a particular feature, you can add a android:required="false" attribute to the <uses-feature> declaration.

For a list of permissions that imply hardware features, see the documentation for the <uses-feature> element.

syntax:

<uses-permission android:name="string"
        android:maxSdkVersion="integer" />

contained in:

<manifest>

description:

Specifies a system permission that the user must grant for the app to operate correctly. The user grants permissions when the application installs, on devices running Android 5.1 and lower, or while the app runs, on devices running Android 6.0 and higher.

For more information on permissions, see the Permissions section in the app manifest overview and the Permissions on Android guide. A list of permissions defined by the base platform is at android.Manifest.permission.

attributes:

android:name

The name of the permission. It can be a permission defined by the application with the <permission> element, a permission defined by another application, or one of the standard system permissions, such as "android.permission.CAMERA" or "android.permission.READ_CONTACTS". As these examples show, a permission name typically includes the package name as a prefix.

android:maxSdkVersion

The highest API level at which this permission is granted to your app. Setting this attribute is useful if the permission your app requires is no longer needed beginning at a certain API level.

For example, beginning with Android 4.4 (API level 19) it's no longer necessary for your app to request the WRITE_EXTERNAL_STORAGE permission to write to its own application-specific directories on external storage, which are provided by getExternalFilesDir().

However, the permission is required for API level 18 and lower. So you can declare that this permission is needed only up to API level 18 with a declaration like the following:

<uses-permission
     android:name="android.permission.WRITE_EXTERNAL_STORAGE"
     android:maxSdkVersion="18" />

This way, beginning with API level 19, the system no longer grants your app the WRITE_EXTERNAL_STORAGE permission.

Added in API level 19.

introduced in:

API level 1

see also: