Home PC Games Linux Windows Database Network Programming Server Mobile  
  Home \ Programming \ Use Android Studio and Gradle packaged multi-version APK     - How to write a new Git protocol (Linux)

- Docker knowledge base (Server)

- How to force Linux users to change the initial password the first time you log in (Linux)

- Summary Linux bond of multi-interface load balancing (Linux)

- Let CentOS6 yum upgrade to support more source rpm package (Linux)

- Elaborate .NET Multithreading: Concepts (Programming)

- MySQL management partition table (Database)

- C ++ overloaded stream insertion operator and the stream extraction operator (Programming)

- Oracle 12C modify spfile path (Database)

- See Linux kernel, CPU, memory, and various versions of the command module and means (Linux)

- Ubuntu users to install voice switch instructs the applet (Linux)

- Oracle Database routine inspection (Database)

- xCAT install and update software (Linux)

- Oracle 11g contraction table space error ORA-03297: file contains used data beyondrequested RESIZE value (Database)

- Hadoop vs spark (Server)

- Let Git variety of colors and custom log format output (Linux)

- In addition to wget and curl, what better alternatives (Linux)

- Java data structures - order linear form of table ArrayList (Programming)

- MySQL concat function is SQL injection (Linux)

- Java Cookie Comments (Programming)

  Use Android Studio and Gradle packaged multi-version APK
  Add Date : 2018-11-21      
  In the project development process, there is often a need to package different versions of APK needs. For example, debug version, release version, dev version and so on. Sometimes different versions to use a different domain name server api is not the same. For example debug_api.com, release_api.com, dev_api.com like.

Different versions corresponding to different api domain may also correspond to different icon and the like.

If every time we have to modify the package before manually modified so that it is not convenient enough.

But if we use Android Studio and Gradle, this trouble can easily be omitted.

Here's how: add the following code to open build.gradle (Module in) the android next node in Android Studio

buildTypes {

    // The name of the custom here, the case is not required
    release {
        // Here is the addition of a suffix applicationId in. So "." To add
        applicationIdSuffix ".release"
        // Here is to select whether obfuscated code
        minifyEnabled false
        proguardFiles getDefaultProguardFile ( 'proguard-android.txt'), 'proguard-rules.pro'

    dev {
        applicationIdSuffix ".dev"
        minifyEnabled false
        proguardFiles getDefaultProguardFile ( 'proguard-android.txt'), 'proguard-rules.pro'


// Here for different versions had set some special parameters, and buildType not directly related.
// For example: Use buildType the dev version, you can also use custom parameters flavors_release set up inside. This requires the development in accordance with their own needs.
productFlavors {

// Custom name but not the same as above buildType, or Gradle compilation fails. As used herein, a "flavors_" prefix to distinguish.
    flavors_release {
    // ManifestPlaceholders wrote of "str", "package_name" does not support the use of capital letters, otherwise Gradle compiler will not pass.
    // Set variable here can be used directly in the "AndroidManifest.xml", the use of: $ {package_name}
    // Android: label = "$ {package_name}"
        manifestPlaceholders = [str: "releaseStr", package_name: "com.sunhz.mvptest.release"]

        // Parameter here is to use java code, the specific use is:. Context.getResources () getString (R.string.strKey);
        resValue ( "string", "strKey", "releaseStrValue")

    flavors_dev {
        manifestPlaceholders = [str: "devStr", package_name: "com.sunhz.mvptest.dev"]

        resValue ( "string", "strKey", "devStrValue")

After completion of the above settings, where we want to use it?

Use the following manner: In Android Studio toolbar, find the "Build" items, find the "Generate Signed APK ..."

Select Module -> Create APK key, or enter the password APK key -> The key here!

In the "BuildType" field, you select two BuildType we set in build.gradle in, respectively, releas, dev, debug. Wherein the "debug" comes to Android Studio.

In the "Flavors" at select two Flavors we set in build.gradle in order to facilitate direct use parameters defined in the build.gradle customized.

and so! Above I have mentioned that, buildType and Flavors no direct contact. They can be used in conjunction with each other according to user needs. As shown above, BuildType selected release, but Flavors choice is flavors_dev.

This basic use on all finished.

There is a problem, playing out different versions of the package, all can be installed on the same phone, all the two packets and can be published to Google's market upswing Why is this?

Here we must mention "applicationIdSuffix" attribute in BuildType we set up, according to the literal translation of this attribute is: "applicationId suffix", then there comes a question, "What is applicationId" is the? In fact, this "applicationId" attribute, in fact, after the completion of the project to create a presence in the build.gradle. In defaultConfig node node under the android. And the same default applicationId and in AndroidManifest.xml package properties.

We can see, the default value of these two properties are the same.

applicationId and they packageName What is the relationship?

After the project is created by default, both the same. If you need to build different versions of APK according to different needs, then we set up "applicationIdSuffix" can do it.

There is a noteworthy phenomenon.

For example, we use a dev type when packaged, packaged software is installed out of the APK to your phone.

Use the following code to get packageName all the programs on our phone.

PackageManager packageManager = mContext.getPackageManager ();
List packageInfoList = packageManager.getInstalledPackages (PackageManager.GET_PERMISSIONS);
List packageNameList = new ArrayList ();
for (PackageInfo packageInfo: packageInfoList) {
    packageNameList.add (packageInfo.packageName);
We print out the information in the package name will appear com.spencer_dev.test.dev. Com.spencer_dev.test did not appear.

but! If decompile tool, APK package decompile directly view the source code, java code where the src directory of the package name, and also, as we have set for com.spencer_dev.test. The package can AndroidManifest.xml and BuildConfig class APPLICATION_ID has become com.spencer_dev.test.dev.

applicationId packageName and what they each represent?

According to the above results, it, package represents the java code package. applicationId represents a unique identification applications. And signed application and other applications together to distinguish different. I think this is why Google market reason to allow the same application of different applicationId.
- Linux System Getting Started Learning: Linux in the last command (Linux)
- CentOS static IP network configuration (Linux)
- Ubuntu 14.04 Fixed update information is outdated error (Linux)
- Oracle 11g RAC installation considerations Miscellany (Database)
- Linux system ARP attack solution (Linux)
- Linux systems for entry-learning - Install Go language in Linux (Linux)
- Nginx Load Balancing (standby) + Keepalived (Server)
- How to create a bootable USB disk to use MultiSystem on Ubuntu (Linux)
- Based Docker build stand-alone high-availability cluster Hadoop2.7.1 Spark1.7 (Server)
- To learn linux security (Linux)
- Bash difference in single quotes and double quotes (Programming)
- Terminal Linux command prints - echo (Linux)
- Linux, Firefox unloading and installation and upgrade (Linux)
- Node.JS different ways to install under Ubuntu 15.04 (Linux)
- Using Linux command line and execute PHP code (Programming)
- A summary of Java multi-threaded programming - acquaintance multithreading (Programming)
- C ++ How to determine the types of constants (Programming)
- Installation of Ubuntu Make under Ubuntu 15.10 (Linux)
- TOAST function in PostgreSQL (Database)
- CentOS 6.5 installation Python3.0 (Linux)
  CopyRight 2002-2022 newfreesoft.com, All Rights Reserved.