Distribute Android apps to testers using Gradle

You can integrate App Distribution into your Android build process using the App Distribution Gradle plugin. The plugin lets you specify your testers and release notes in your app's build.gradle file, letting you configure distributions for different build types and variants of your app.

This guide describes how to distribute APKs to testers using the App Distribution Gradle plugin.

Before you begin

If you haven't already, add Firebase to your Android project.

If you aren't using any other Firebase products, you only have to create a project and register your app. However, if you decide to use additional products in the future, be sure to complete all of the steps on the page linked above.

Step 1. Set up your Android project

1. In your project-level Gradle file (usually android/build.gradle), add the App Distribution plugin as a buildscript dependency:

   buildscript {
       repositories {
           // Check that you have Google's Maven repository (if not, add it).
           google()
           jcenter()
       }
       dependencies {
           // Add the App Distribution Gradle plugin
           classpath 'com.google.firebase:firebase-appdistribution-gradle:2.2.0'
       }
   }
   

2. In your app-level Gradle file (usually android/app/build.gradle), include the App Distribution plugin below the Android plugin:

   apply plugin: 'com.android.application'
   // ...
   
   // Apply the App Distribution Gradle plugin
   apply plugin: 'com.google.firebase.appdistribution'
   // ...
   

3. If you're behind a corporate proxy or firewall, add the following Java system property that enables App Distribution to upload your distributions to Firebase:

   -Djavax.net.ssl.trustStore=/path/to/truststore -Djavax.net.ssl.trustStorePassword=password
   

Step 2. Authenticate with Firebase

Before you can use the Gradle plugin, you must first authenticate with your Firebase project. There are three ways to achieve this:

Step 3. Configure your distribution properties

1. In your app/build.gradle file, configure App Distribution by adding at least one firebaseAppDistribution section. For example, to distribute the release build to testers:

   android {
   
       // ...
   
       buildTypes {
           release {
               firebaseAppDistribution {
                   artifactType="APK"
                   releaseNotesFile="/path/to/releasenotes.txt"
                   testers="ali@example.com, bri@example.com, cal@example.com"
               }
           }
       }
   
       // ...
   }
   

2. App Distribution can be configured for build types and product flavors. For example, to distribute debug and release builds in "demo" and "full" product flavors:

   android {
   
       // ...
   
       buildTypes {
           debug {...}
           release {...}
       }
   
       flavorDimensions "version"
       productFlavors {
         demo {
             dimension "version"
             firebaseAppDistribution {
                 releaseNotes="Release notes for demo version"
                 testers="demo@testers.com"
             }
         }
         full {
             dimension "version"
             firebaseAppDistribution {
                 releaseNotes="Release notes for full version"
                 testers="full@testers.com"
             }
         }
       }
   
       // ...
   }
   

3. Use the following parameters to configure the distribution:

appId="1:1234567890:android:321abc456def7890"

testers="ali@example.com, bri@example.com, cal@example.com"

testersFile="/path/to/testers.txt"

groups="qa-team, android-testers"

groupsFile="/path/to/tester-groups.txt"

Step 4. Distribute your app to testers

Finally, to package your test app and invite testers, build the targets assembleBUILD-VARIANT and appDistributionUploadBUILD-VARIANT with your project's Gradle wrapper, where BUILD-VARIANT is the optional product flavor and build type you configured in the previous step. For more information about product flavors, see Configure build variants.

For example, to distribute your app using the release build variant, run the following command:

./gradlew assembleRelease appDistributionUploadRelease

Or, if you authenticated with your Google Account and didn't provide credentials in your Gradle build file, include the FIREBASE_TOKEN variable:

export FIREBASE_TOKEN=1/a1b2c3d4e5f67890
./gradlew --stop // Only needed for environment variable changes
./gradlew assembleRelease appDistributionUploadRelease

You can also override the values set in your build.gradle file by passing command line arguments in the form of -PappDistribution-<property-name>=<property-value>. For example:

./gradlew bundleDebug appDistributionUploadDebug
    -PappDistribution-artifactType="APK"

Once you distribute your build, it becomes available in the App Distribution dashboard of the Firebase console for 150 days (five months). When the build is 30 days from expiring, an expiration notice appears in both the console and your tester's list of builds on their test device.

Testers who haven't been invited to test the app receive email invitations to get started, and existing testers receive email notifications that a new build is ready to test (read the tester set up guide for instructions on how to install the test app). You can monitor the status of each tester-whether they accepted the invitation and whether they downloaded the app-in the Firebase console.

Next step

Visit the Android App Bundle codelab to learn how to distribute app bundle releases step by step.