<manifest xmlns:android="http://schemas.android.com/apk/res/android" package="string" android:sharedUserId="string" android:sharedUserLabel="string resource" android:versionCode="integer" android:versionName="string" android:installLocation=["auto" | "internalOnly" | "preferExternal"] > . . . </manifest>
- contained in:
- must contain:
- can contain:
- The root element of the AndroidManifest.xml file. It must
<application>element and specify
- Defines the Android namespace. This attribute should always be set
- The value of the
packageattribute in the APK's manifest file represents your app's universally unique application ID. It has to be formatted as a full Java-language-style package name for the Android app. The name may contain uppercase or lowercase letters ('A' through 'Z'), numbers, and underscores ('_'). However, individual package name parts may only start with letters.
You should be careful not to change the
packagevalue, since that essentially creates a new app and users of the previous version of your app will not receive an update, nor be able to transfer their data between the old and new versions.
In the Gradle-based build system, starting with AGP 7.3, you shouldn't set the
packagevalue in the source manifest file directly. For more information, see Set the application ID.
This constant was deprecated in API level 29.
Shared user IDs cause non-deterministic behavior within the package manager. As such, its use is strongly discouraged and may be removed in a future version of Android. Instead, apps should use proper communication mechanisms, such as services and content providers, to facilitate interoperability between shared components. Note that existing apps cannot remove this value, as migrating off a shared user ID is not supported. These apps should add
android:sharedUserMaxSdkVersion="32"to avoid using shared user ID on new user installs.
The name of a Linux user ID that will be shared with other apps. By default, Android assigns each app its own unique user ID. However, if this attribute is set to the same value for two or more apps, they will all share the same ID — provided that their certificate sets are identical. Apps with the same user ID can access each other's data and, if desired, run in the same process.
The target sandbox for this app to use. The higher the sandbox version number,
the higher the level of security.
Its default value is
1; you can also set it to
2. Setting this attribute to
2switches the app to a different SELinux sandbox.
The following restrictions apply to a level 2 sandbox:
- The default value of
usesCleartextTrafficin the Network Security Config is false.
- Uid sharing is not permitted.
For Android Instant Apps targeting Android 8.0 (API level 26) or higher, this attribute must be set to 2. You can set the sandbox level in the installed version of your app to the less restrictive level 1, but if you do so, your app does not persist app data from the instant app to the installed version of your app. You must set the installed app's sandbox value to 2 in order for the data to persist from the instant app to the installed version.
Once an app is installed, you can only update its target sandbox value to a higher value. To downgrade the target sandbox value, you must uninstall the app and replace it with a version whose manifest contains a lower value for this attribute.
- The default value of
This constant was deprecated in API level 29.
Shared user IDs cause non-deterministic behavior within the package manager. As such, its use is strongly discouraged and may be removed in a future version of Android. Instead, apps should use proper communication mechanisms, such as services and content providers, to facilitate interoperability between shared components. Note that existing apps cannot remove this value, as migrating off a shared user ID is not supported.
A user-readable label for the shared user ID. The label must be set as a reference to a string resource; it cannot be a raw string.
This attribute was introduced in API Level 3. It is meaningful only if the
sharedUserIdattribute is also set.
- An internal version number. This number is used only to determine whether
one version is more recent than another, with higher numbers indicating more
recent versions. This is not the version number shown to users; that number
is set by the
The value must be set as a positive integer greater than 0. You can define it however you want, as long as each successive version has a higher number. For example, it could be a build number. Or you could translate a version number in "x.y" format to an integer by encoding the "x" and "y" separately in the lower and upper 16 bits. Or you could simply increase the number by one each time a new version is released.
- The version number shown to users. This attribute can be set as a raw
string or as a reference to a string resource. The string has no other purpose
than to be displayed to users. The
versionCodeattribute holds the significant version number used internally.
- The default install location for the app.
The following keyword strings are accepted:
Value Description "
The app must be installed on the internal device storage only. If this is set, the app will never be installed on the external storage. If the internal storage is full, then the system will not install the app. This is also the default behavior if you do not define
The app may be installed on the external storage, but the system will install the app on the internal storage by default. If the internal storage is full, then the system will install it on the external storage. Once installed, the user can move the app to either internal or external storage through the system settings. "
The app prefers to be installed on the external storage (SD card). There is no guarantee that the system will honor this request. The app might be installed on internal storage if the external media is unavailable or full. Once installed, the user can move the app to either internal or external storage through the system settings.
Note: By default, your app will be installed on the internal storage and cannot be installed on the external storage unless you define this attribute to be either "
auto" or "
When an app is installed on the external storage:
.apkfile is saved to the external storage, but any app data (such as databases) is still saved on the internal device memory.
- The container in which the
.apkfile is saved is encrypted with a key that allows the app to operate only on the device that installed it. (A user cannot transfer the SD card to another device and use apps installed on the card.) Though, multiple SD cards can be used with the same device.
- At the user's request, the app can be moved to the internal storage.
The user may also request to move an app from the internal storage to the external storage. However, the system will not allow the user to move the app to external storage if this attribute is set to
internalOnly, which is the default setting.
Read App Install Location for more information about using this attribute (including how to maintain backward compatibility).
Introduced in: API Level 8.
- introduced in:
- API Level 1 for all attributes, unless noted otherwise in the attribute description.
- see also: