Signing product flavors with gradle

后端 未结 3 1488
梦毁少年i
梦毁少年i 2020-11-29 22:56

I am tyring to migrate my projects to gradle. One of my projects has multiple product flavors and each one of them has to be signed with a different signingConfig

相关标签:
3条回答
  • 2020-11-29 23:26

    The gradle plugin for android only supports signing per build type, not per flavor. The reason for this is that any given variant (build type + flavors) can only be signed by one key, but can be a combination of several flavor groups. For example your flavor groups could be cpu (x86/arm) and version (free/paid), that's four different variants right there.

    The solution you're looking for is to create separate build types for your different release versions. For example, your build types might be debug, release, release-beta, like this:

    ...
    
    android {
    
        ...
    
        buildTypes {
            debug {
                signingConfig signingConfigs.debug
            }
    
            release {
                signingConfig signingConfigs.release
            }
    
            release-beta {
                initWith release
                signingConfig signingConfigs.release-beta
            }
        }
    }
    

    The initWith above just tells gradle that release-beta should be a copy of the release build type, only signed with a different key.

    0 讨论(0)
  • 2020-11-29 23:28

    Per the user guide, signingConfigs for flavors are supported.

    The problem here has to do with the scope of the signingConfigs object. I just assigned it to a variable inside the productFlavors block, but outside the flavor1 flavor block to fix the issue:

    productFlavors {
        def flavor1SigningVariable = signingConfigs.flavor1
    
        flavor1 {
            ...
            signingConfig flavor1SigningVariable
            ...
        }
    
    0 讨论(0)
  • 2020-11-29 23:32

    You can declare signing config for each flavor in buildType. Here is my gradle file for release signing flavors with different keystores.

    android {
      signingConfigs {
        configFirst {
            keyAlias 'alias'
            keyPassword 'password'
            storeFile file('first.keystore')
            storePassword 'password'
        }
    
        configSecond {
            keyAlias 'alias'
            keyPassword 'password'
            storeFile file('second.keystore')
            storePassword 'password'
        }
      }
    
      compileSdkVersion 23
      buildToolsVersion "23.0.2"
      defaultConfig {
            minSdkVersion 14
            targetSdkVersion 23
      }
    
      productFlavors{
        flavor1 {
            applicationId "com.test.firstapp"
        }
    
        flavor2 {
            applicationId "com.test.secondapp"
        }
      }
    
      buildTypes {
        release {
            productFlavors.flavor1.signingConfig signingConfigs.configFirst
            productFlavors.flavor2.signingConfig signingConfigs.configSecond           
    
            minifyEnabled true
            proguardFiles getDefaultProguardFile('proguard-android.txt'),
                    'proguard-rules.pro'
    
        }
      }
    }
    

    buildTypes block should be placed after productFlavors block, I mean order is important.

    0 讨论(0)
提交回复
热议问题