Deploying Android Apps Using GitHub Actions

May 4 2023 · Kotlin 1.7.21, Android 13, Android Studio Electric Eel

Part 1: Automate Releases with GitHub Actions

09. Release to the Google Play Store

Episode complete

About this episode

Leave a rating/review

See forum comments
Cinema mode Mark complete Download course materials
Previous episode: 08. Authenticate with Google Play Console

Get immediate access to this and 4,000+ other videos and books.

Take your career further with a Kodeco Personal Plan. With unlimited access to over 40+ books and 4,000+ professional videos in a single subscription, it's simply the best investment you can make in your development career.

Learn more Already a subscriber? Sign in.

Notes: 09. Release to the Google Play Store

Try writing a changelog for different releases of your app and upload it along with the APK. You can find out more at

Heads up... You've reached locked video content where the transcript will be shown as obfuscated text.

To upload a build to the Play Store Console, use the r0adkll/upload-google-play action.

Job to Upload to Google Play

To do this, create a new file named play_store_workflow.yml under .github/workflows and add the following code to it:

name: Deploy to Play Store

      - master

    needs: [build]
    runs-on: ubuntu-latest
      - uses: actions/download-artifact@v3
          name: release.aab
      - uses: actions/download-artifact@v3
          name: mapping.txt
      - name: Publish to Play Store internal test track
        uses: r0adkll/upload-google-play@v1.1.1
          serviceAccountJsonPlainText: ${{ secrets.PLAY_SERVICE_ACCOUNT_JSON }}
          releaseFiles: app-release-signed.aab
          track: internal
          changesNotSentForReview: true
          mappingFile: mapping.txt

Verify the Uploaded Build

To verify the workflow, push an empty commit to the master branch.

git commit --allow-empty -m "Empty commit"
git push origin master