如何使用Azure Pipeline签名Android App Bundle？签AAB时遇报错求助

I’ve run into this exact hiccup before—since the official Azure Pipeline Android Signing task is built primarily for APKs, it stumbles with AABs because it can’t locate the AndroidManifest.xml in the bundle’s structure to auto-detect the min SDK version. Here are three reliable fixes to get your AAB signed successfully:

1. Manually Specify the Min SDK Version in the Android Signing Task #

The quickest fix is to bypass the task’s auto-detection by explicitly adding the min SDK parameter:

• Edit your pipeline’s Android Signing task
• Locate the Additional arguments field (usually near the bottom of the task settings)
• Input --min-sdk-version <your_min_sdk_version> (replace <your_min_sdk_version> with your app’s actual minimum SDK, e.g., --min-sdk-version 21)

This tells the task exactly which SDK version to use, skipping the failed auto-deduction step.

2. Use jarsigner Directly via a Command Line Task #

Since the Android Signing task is just a wrapper around jarsigner, you can skip the task entirely and run the signing command yourself for more control:

1. Add a Command Line task to your pipeline right after the AAB is built
2. Use this command (swap the pipeline variables with your actual values):

jarsigner -verbose -sigalg SHA256withRSA -digestalg SHA-256 -keystore $(KeystoreFilePath) -storepass $(KeystorePassword) -keypass $(KeyPassword) $(AABFileOutputPath) $(KeyAlias)

Make sure all variables (like $(KeystoreFilePath)) are configured in your pipeline’s variable group or task variables, just like you would for the official signing task.

3. Sign the AAB Directly in Your Gradle Build (Recommended) #

The most seamless approach is to integrate signing into your Gradle build process, so the AAB is signed during the build step itself—no separate signing task needed:

• In your app module’s build.gradle (or build.gradle.kts) file, add a signing config that pulls credentials from pipeline environment variables:

android {
    signingConfigs {
        release {
            storeFile file(System.getenv("KEYSTORE_FILE_PATH"))
            storePassword System.getenv("KEYSTORE_PASSWORD")
            keyAlias System.getenv("KEY_ALIAS")
            keyPassword System.getenv("KEY_PASSWORD")
        }
    }
    buildTypes {
        release {
            signingConfig signingConfigs.release
        }
    }
}

• Update your pipeline’s Gradle task to run bundleRelease (instead of just assembling without signing)
• Configure the required environment variables (KEYSTORE_FILE_PATH, KEYSTORE_PASSWORD, etc.) in your pipeline variables

This method avoids the compatibility issue altogether because Gradle natively supports signing AABs, and you don’t have to rely on the Azure Pipeline task’s APK-focused logic.

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