Upload Android release to the Play Store

This action will help you upload an Android .apk or .aab (Android App Bundle) file to the Google Play Console using the Google Play Developer API v3.

Inputs

You must provide one of either serviceAccountJson or serviceAccountJsonPlainText

`serviceAccountJson`

The service account json private key file to authorize the upload request

`serviceAccountJsonPlainText`

The service account json in plain text, provided via a secret, etc.

`packageName`

Required: The package name, or Application Id, of the app you are uploading

`releaseFile`

Required: The Android release file to upload (.apk or .aab)

`track`

Required: The track in which you want to assign the uploaded app.
Default: production
Values: alpha, beta, internal, production

`userFraction`

Portion of users who should get the staged version of the app. Accepts values between 0.0 and 1.0 (exclusive-exclusive). Omitting this value will execute a full rollout.

The directory of localized whats new files to upload as the release notes. The files contained in the whatsNewDirectory MUST use the pattern whatsnew-<LOCALE> where LOCALE is using the BCP 47 format, e.g.

en-US - English/America
de-DE - German/Germany
ja-JP - Japanese/Japan

and contain plain utf8 encoded text with no extension on the file. The resulting directory in your project should look something like this:

projectDir/
└── whatsNewDirectory/
    ├── whatsnew-en-US
    ├── whatsnew-de-DE
    └── whatsnew-ja-JP

where whatsNewDirectory is the path you pass to the action.

`mappingFile`

The mapping.txt file used to de-obfuscate your stack traces from crash reports

Example usage

uses: r0adkll/upload-google-play@v1
with:
  serviceAccountJson: ${{ SERVICE_ACCOUNT_JSON }}
  packageName: com.example.MyApp
  releaseFile: ${{ SIGNED_RELEASE_FILE}}
  track: beta
  userFraction: 0.33
  whatsNewDirectory: /distribution/whatsnew
  mappingFile: /app/build/outputs/mapping/release/mapping.txt

Authentication

How to make serviceAccountJson and serviceAccountJsonPlainText

First you have to create a Google Play API Access. To do that go to the Google Play Developer Console and then with the account owner go to Settings -> API access and create a Google Play Android Developer project.

After that follow the instructions to create a Service Account. When you click Create Client ID, choose Service Account. You will get a JSON file with a public key and the service email.

Google Play publisher account

For the initial setup only, you must have access to the Google account which owns the [Google Play publisher account][gp-docs-distribute].

This is required to enable API access from GitHub Actions to your Google Play account.

Note that having admin access is not enough; you need the account owner.
You can see who the account owner is under [Settings → User accounts & rights][gp-console-admin] in the Google Play developer console.

Please note

The app being uploaded must already exist in Google Play; you cannot use the API to upload brand new apps

Bundle size warnings

If you try to upload an AAB file to Google Play (including manually via the Google Play Developer Console), and its size is perhaps 100MB+, it may give you a warning:

The installation of the app bundle may be too large and trigger user warning on some […] this needs to be explicitly acknowledged

This plugin automatically "acknowledges" that warning on Google Play on your behalf when uploading any AAB files, regardless of their size, so you should not see any errors.

If you do see see any unexpected behaviour related to uploading bundles, or warnings appearing for end users, please let us know.

Sign in to the [Google Play developer console][gp-console] as the account owner
Select Settings → Developer account → API access
Under Service Accounts, click "Create Service Account"
Follow the link to the Google API Console
Click the "Create service account" button
Give the service account any name you like, e.g. "Github Actions"
Choose Service Accounts > Service Account User （中文搜尋要用[服務帳戶使用者]） for the "Role" field
Enable "Furnish a new private key"
Choose "JSON" as the key type (P12 works as well, but the Plugin suppter a JSON is a little simpler)
Click the "Save" button
Note that a .json file is downloaded, named something like "api-xxxxxxxxx-xxxxx-xxxx.json"
Close the dialog that appears
Copy the email address of the new user (something like "Github Actions@api-xxxxxxxxx-xxxxx-xxxx.iam.gserviceaccount.com")
You can now close the page

Assign permissions to the service account

Return to the Google Play developer console page
Click "Done" on the dialog
Note that the service account has been associated with the Google Play publisher account
If it hasn't, follow these additional steps before continuing:
1. Click "Users & permissions" in the menu
2. Click "Invite new user"
3. Paste in the email address you copied above
4. Continue from step 5
Click the "Grant access" button for the account (e.g. "Github Actions@api-xxxxxxxxx-xxxxx-xxxx.iam.gserviceaccount.com")
Ensure that at least the following permissions are enabled:
- View app information — this is required for the plugin to function
- Manage production releases — optional, if you want to upload APKs to production
- Manage testing track releases — if you want to upload APKs to alpha, beta, internal, or custom test tracks
Click "Add user" (or "Send invitation", as appropriate)
You can now log out of the Google Play publisher account

To do so, visit Google Play Console to set up API access and don’t forget to click Grant Access when you are done.

Refer to

https://github.com/jenkinsci/google-play-android-publisher-plugin/blob/master/README.md https://medium.com/@iqan/continuously-releasing-flutter-app-to-play-store-using-github-actions-eca2f5f6e996

CS6/upload-google-play