Alright, I get why you're confused—Android Studio's graphical Generate Signed APK/Bundle wizard doesn't show options for Signature Scheme v3 and v4 yet. Don't worry though, you have two reliable ways to enable these signatures: using Gradle configurations or the apksigner command-line tool. Let's break both down step by step:

This is the most straightforward method if you're using Android Studio with Gradle builds. Just add the v3 and v4 signing flags to your module's build configuration:

1. Open your app module's build.gradle (or build.gradle.kts if you use Kotlin DSL) file.
2. Locate the signingConfigs block for your release build, and add the enable flags for v3 and v4:

android {
    signingConfigs {
        release {
            storeFile file("your-keystore-path.jks") // Replace with your keystore path
            storePassword "your-store-password" // Replace with your store password
            keyAlias "your-key-alias" // Replace with your key alias
            keyPassword "your-key-password" // Replace with your key password
            
            // Enable all signature schemes
            v1SigningEnabled true
            v2SigningEnabled true
            v3SigningEnabled true
            v4SigningEnabled true
        }
    }

    buildTypes {
        release {
            signingConfig signingConfigs.release
            // Keep your existing build type configs here
        }
    }
}

3. Sync your Gradle project (click the "Sync Now" prompt or use File > Sync Project with Gradle Files).
4. Build your release APK or App Bundle as usual—Gradle will automatically apply v3 and v4 signatures along with v1 and v2.

If you prefer manual control or need to sign an existing APK, use the apksigner tool included with the Android SDK Build Tools.

Signing the APK with v3 and v4 #

1. First, navigate to the location of apksigner in your terminal. It's usually in $ANDROID_HOME/build-tools/<version>/ (replace <version> with your installed Build Tools version, e.g., 34.0.0).
2. Run the following command to sign your APK, enabling v3 and v4:

apksigner sign --ks your-keystore.jks --ks-key-alias your-key-alias --v3-enabled true --v4-enabled true path-to-your-app.apk

3. When prompted, enter your keystore password and key password.

Verifying the Signatures #

To confirm that v3 and v4 signatures were applied successfully, run:

apksigner verify --verbose path-to-your-app.apk

Look for lines like Verified using v3 scheme and Verified using v4 scheme in the output—this confirms the signatures are active.

Note: v4 signature generates an additional .idsig file alongside your APK. You'll need to upload this file to Google Play when submitting your app, as it helps optimize app delivery.

内容的提问来源于stack exchange，提问作者Nabzi