Skip to content Skip to sidebar Skip to footer
Página inicial / Can I Change My Package Name After Apk Is Uploaded

Can I Change My Package Name After Apk Is Uploaded

Postar um comentário

<manifest>

syntax:
<manifest xmlns:android="http://schemas.android.com/apk/res/android"           parcel="string"           android:sharedUserId="string"           android:sharedUserLabel="cord resource"                                    android:versionCode="integer"           android:versionName="string"           android:installLocation=["auto" | "internalOnly" | "preferExternal"] >     . . . </manifest>
contained in:
none
must comprise:
<awarding>
can contain:
<compatible-screens>
<instrumentation>
<permission>
<permission-group>
<permission-tree>
<queries>
<supports-gl-texture>
<supports-screens>
<uses-configuration>
<uses-characteristic>
<uses-permission>
<uses-permission-sdk-23>
<uses-sdk>
description:
The root element of the AndroidManifest.xml file. It must contain an <application> element and specify xmlns:android and package attributes.
attributes:
xmlns:android
Defines the Android namespace. This attribute should always be ready to "http://schemas.android.com/apk/res/android".
package
A total 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 beginning with messages.

While building your app into the an application parcel (APK), the build system uses the package attribute for 2 things:

  • Information technology applies this name as the namespace for your app'due south generated R.java class (used to access your app resources).

    For example, if package is set to "com.example.myapp", the R grade is created at com.example.myapp.R.

  • It uses this name to resolve whatever relative course names that are declared in the manifest file.

    For instance, if package is set to "com.example.myapp", an activity alleged as <activeness android:proper noun=".MainActivity"> is resolved to be com.example.myapp.MainActivity.

This proper name is as well the default proper noun for your app process (come across the <awarding> element's procedure attribute). And it'due south the default chore affinity for your activities (come across the <activity> element's taskAffinity aspect).

This name as well represents the awarding ID, which must be universally unique in society to publish your app in Google Play. However, toward the end of the build process, the build tools override the package proper noun using the applicationId property from the build.gradle file (used by Android Studio projects). Every bit long as you keep the manifest'due south bundle proper noun the same as the build file's applicationId, this won't be a concern. Just if these ii values differ, y'all should sympathize the differences between the "packet proper noun" and "awarding ID" by reading how to set the application ID.

To avoid conflicts with other developers, you should use Internet domain buying as the footing for your package names (in reverse). For example, apps published by Google start with com.google.

Note: Both the com.instance and com.android namespaces are forbidden by Google Play.

If you want to change your packet name after you publish your app, you lot can, but you must keep the applicationId the same. The applicationId defines the unique identity for your app on Google Play. So if you modify it, the new app is considered to be a different app and users of the previous version will not receive an update. For more than information, see how to set the application ID.

android:sharedUserId

This constant was deprecated in API level 29.
Shared user IDs cause non-deterministic behavior within the package manager. As such, its apply is strongly discouraged and may be removed in a future version of Android. Instead, apps should use proper advice 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 non supported.

The proper noun of a Linux user ID that volition exist 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 information and, if desired, run in the aforementioned procedure.

android:targetSandboxVersion
The target sandbox for this app to use. The college the sandbox version number, the higher the level of security. Its default value is i; you lot can besides gear up it to 2. Setting this aspect to 2 switches the app to a different SELinux sandbox.

The following restrictions apply to a level ii sandbox:

  • The default value of usesCleartextTraffic in the Network Security Config is fake.
  • Uid sharing is non permitted.

For Android Instant Apps targeting Android 8.0 (API level 26) or higher, this attribute must be ready to 2. You can set up the sandbox level in the installed version of your app to the less restrictive level one, but if you practise so, your app does not persist app data from the instant app to the installed version of your app. You lot must set the installed app'south sandbox value to 2 in social club 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 college value. To downgrade the target sandbox value, you must uninstall the app and supplant it with a version whose manifest contains a lower value for this aspect.

android:sharedUserLabel

This constant was deprecated in API level 29.
Shared user IDs cause not-deterministic behavior inside the parcel manager. Every bit such, its use is strongly discouraged and may be removed in a hereafter version of Android. Instead, apps should apply proper communication mechanisms, such equally services and content providers, to facilitate interoperability betwixt 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 gear up as a reference to a string resource; information technology cannot be a raw string.

This attribute was introduced in API Level iii. It is meaningful only if the sharedUserId attribute is also set up.

android:versionCode
An internal version number. This number is used just to determine whether one version is more recent than another, with higher numbers indicating more recent versions. This is non the version number shown to users; that number is set by the versionName attribute.

The value must exist set every bit a positive integer greater than 0. You can define it even so you lot desire, as long equally each successive version has a college number. For case, 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 ane each time a new version is released.

android:versionName
The version number shown to users. This attribute can be fix equally a raw string or as a reference to a cord resource. The string has no other purpose than to be displayed to users. The versionCode aspect holds the pregnant version number used internally.
android:installLocation
The default install location for the app.

The following keyword strings are accustomed:

Value Clarification
"internalOnly" 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 organisation will not install the app. This is too the default behavior if you lot exercise not ascertain android:installLocation.
"auto" The app may be installed on the external storage, simply the system will install the app on the internal storage by default. If the internal storage is total, then the organisation will install it on the external storage. One time installed, the user tin move the app to either internal or external storage through the arrangement settings.
"preferExternal" The app prefers to exist installed on the external storage (SD carte du jour). There is no guarantee that the organization will award this request. The app might be installed on internal storage if the external media is unavailable or full. Once installed, the user can motion the app to either internal or external storage through the system settings.

Notation: Past default, your app will be installed on the internal storage and cannot be installed on the external storage unless you define this aspect to be either "auto" or "preferExternal".

When an app is installed on the external storage:

  • The .apk file is saved to the external storage, just any app data (such every bit databases) is nevertheless saved on the internal device memory.
  • The container in which the .apk file 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'south request, the app can be moved to the internal storage.

The user may also request to motility an app from the internal storage to the external storage. However, the system volition not allow the user to motility the app to external storage if this attribute is fix to internalOnly, which is the default setting.

Read App Install Location for more information nigh 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 aspect clarification.
meet as well:
<awarding>

guzmanwhard1986.blogspot.com

Source: https://developer.android.com/guide/topics/manifest/manifest-element

Postar um comentário for "Can I Change My Package Name After Apk Is Uploaded"