Note: Google Play uses the <uses-library> elements declared in your app manifest to filter your app from devices that don't meet its library requirements. For more information about filtering, see the topic Google Play filters.
<uses-library android:name="string" android:required=["true" | "false"] />
- contained in:
Specifies a shared library that the application must be linked against. This element tells the system to include the library's code in the class loader for the package.
All of the
androidpackages (such as
android.widget) are in the default library that all applications are automatically linked against. However, some packages (such as
maps) are in separate libraries that are not automatically linked. Consult the documentation for the packages you're using to determine which library contains the package code.
The order of
<uses-library>tags is significant: it affects class lookup and resolution order when the application is being loaded. Some of the libraries may have duplicate classes, and in that case the library that comes first takes priority.
This element also affects the installation of the application on a particular device and the availability of the application on Google Play:
If this element is present and its
android:requiredattribute is set to
PackageManagerframework won't let the user install the application unless the library is present on the user's device.
android:requiredattribute is described in detail in the following section.
The name of the library. The name is provided by the
documentation for the package you are using. An example of this is
android.test.runner", a package that contains Android test classes.
Boolean value that indicates whether the application requires the
library specified by
"true": The application does not function without this library. The system will not allow the application on a device that does not have the library.
"false": The application can use the library if present, but is designed to function without it if necessary. The system will allow the application to be installed, even if the library is not present. If you use
"false", you are responsible for checking at runtime that the library is available.
To check for a library, you can use reflection to determine if a particular class is available.
The default is
Introduced in: API Level 7.
- introduced in:
- API Level 1
- see also: