Publish to Google Play Shop

  • Commodity
  • seven minutes to read

Publish an update to Google Play Shop, including the Blastoff and Beta tracks from App Middle.

Prerequisites

  • Google requires the first version of your Google Play awarding to be published to product through the Google console.
  • A Google Play Developer account. If you don't have one, you can sign up at the Google developer account portal.
  • Ensure that yous have an API project and a Service account for App Center to create a Google Shop connection and to access Google APIs on your behalf.
  • Review prerequisites for Beta and Alpha for more data on these tracks.
  • Prepare App signing past Google to publish Android App bundles .aab files.

For more information, review How to apply the Google Play panel.

Linking your API Project

To admission the Google API, link your Google Play Console to a Google API project. In near cases, we recommend y'all create a new API projection, although current API users tin link to an existing API project. Keep in mind that each API project can only exist linked to a single Google Play Console account.

Creating a new API project

  • Become to the Google API Access page on the Google Play Console.
  • Have the Terms of Service.
  • Click on Create new projection.
  • An API project is automatically generated and linked to your Google Play Panel.

Using an existing API projection

  • If you're already a user of the Google Play Developer API, you can link to your existing API projection past post-obit these steps. If the API project to link to isn't listed, verify that your Google Play Console business relationship is designated as an Possessor, and the Google Play Developer API is enabled.
  • Go to the Google API Access folio on the Google Play Panel.
  • Accept the API Terms of Service.
  • Cull the project you lot want to link.
  • Click on Link.

Setting Upwardly API Admission Clients

One of the added benefits of creating a Google service account is access to the API from a build server without providing your personal user credentials, beneath is a stride-by-step guide on how to fix Google service business relationship:

Go to the Google API Access page on the Google Play Panel.

Google Play: configuring API access

Nether Service Accounts, click the Create Service Account push button to brainstorm the process.

Google Play: Create a service account button highlighted

In the instructions, click the link to the Google API Console.

Google Play: Create Service Account instructions

Click the CREATE SERVICE ACCOUNT button, on the newly opened folio.

Google Play: Service Accounts

The Create service account page opens.

Google Play: Create Service Account Dialog

Choose a proper name for the new Service Business relationship, and click Create.

Google Play: Choose Project -> Owner as role

Click the Select a role in the drop-down carte. Select Projection, then Owner. Navigate to the side by side step by clicking Go along.

Notation

Some users can't download the .json file using Edge and Internet Explorer.

On the new page, click + Create Primal (optional) and a modal appears.

Google Play: Click + Create Key to generate a JSON file

Select JSON and click CREATE and a file with the .json extension will download to your organization; this file will exist used in App Heart to establish the connexion to Google Play.

Google Play: Set key type as JSON

Once you've created the service business relationship on the Google Developers Panel, click Done. The API Access folio automatically refreshes, and your service account will be listed.

Google Play: Service Account Created

Close the window and the new service account shows on the original page. Click the Grant Access push button to complete the procedure. In the next department, you'll learn how to connect App Center with Google Play.

Google Play: Original screen with new service account

Fix up app signing by Google

  1. Select your app in the Google Play Developer Console
  2. Select App signing in the left-paw card
  3. You tin choose between three options:
    1. Upload a primal exported from Android Studio
    2. Export and upload a key from a Java keystore
    3. Export and upload a key (not using a Java keystore)
    4. App signing by Google Play (Recommended)
  4. Click finish

Create a Google Play connection in App Center

  1. Click on Stores under Distribute in the left menu.
  2. In the middle of the page, click on the Connect to Store button.
  3. Select Google Play store.
  4. Click on Next.
  5. Upload the private central JSON file, which you downloaded while creating the service account. If the JSON fields are edited to incorrect values, the shop creation might fail. Make sure you accept the service business relationship linked to your Google Play Developer console equally per the prerequisite section to a higher place.
  6. Once the file is uploaded, click Connect.
  7. A Google Play connexion should at present be visible with the three tracks, Production, Alpha, and Beta in the Stores home page. Setting up this connectedness is a 1 fourth dimension procedure for an app in App Center.

Publish your AAB to the Google Play Store

  1. From the Stores home page, select any of the tracks created to a higher place.
  2. Click on Publish to Store on the button in the upper-right corner.
  3. Upload the app packet. A few points to notation:
    • Application must be prepared for release and signed with a valid key store before uploading.
    • Google Play Shop supports android app bundles up to a maximum of 2 GB. .apk files generated from the .aab can't exceed 150 MB. You can read more about your options at Google's docs for AAB.
    • The version of the .aab must be strictly greater than the current version in production.
    • If you have app versions in other tracks similar Alpha and Beta, your release version should be strictly less than versions in Blastoff and Beta track versions.
    • App Centre doesn't support promoting an app from one track to another. You can't promote a version from blastoff to beta or beta to product.
    • If y'all accept a typhoon release in the track you'll publish to, that draft release volition disappear in favor of the new release y'all publish.
  4. After uploading your package, you tin run into some details of the awarding. Click Adjacent.
  5. Click on Publish to push the app to the Google Play Store. The condition for this release on the Distribute Store Details page volition testify every bit Submitted.
  6. One time App Center has completed the handover of the app to Google, the status of the app volition change to Published. Google could take up to 24 hours to show the app in the Play store.
  7. In case publishing by Google fails, the app owner receives a notification to the registered Google mail.

Publish your APK to the Google Play Store

  1. From the Stores home page, select any of the tracks created higher up.
  2. Click on Publish to Store on the push in the upper-right corner.
  3. Upload the app parcel. A few points to note:
    • Application must be prepared for release and signed with a valid key store before uploading.
    • Google Play Store supports application packages upwardly to a maximum of 100 MB. Upload expansion files directly to the Google Play Console if the awarding exceeds 100 MB. Read Google's doc on expansion files to set it up.
    • The .apk must be zipaligned during the app-building process.
    • The version of the .apk must be strictly greater than the current version in production.
    • If you have app versions in other tracks like Alpha and Beta, your release version should be strictly less than versions in alpha and Beta rails versions.
    • App Heart doesn't support promoting an app from ane track to another. You can't promote a version from alpha to beta or beta to production.
    • If y'all take a draft release in the runway y'all'll publish to, it will be overwritten by the new release.
  4. After uploading your parcel, y'all tin run into some details of the application. Click Side by side.
  5. Click on Publish to button the app to the Google Play Store. The condition for this release on the Distribution Shop Details page will show as Submitted.
  6. Once App Eye has completed the handover of the app to Google, the condition of the app volition change to Published. Google could accept upwardly to 24 hours to show the app in the Play shop.
  7. In case publishing by Google fails, the app owner receives a notification to the registered Google mail.

Publishing through the CLI

Warning

Y'all need App Eye CLI 2.7 or newer to use this characteristic.

Using the CLI is an easy way to integrate the App Center's shop connection as part of your CI/CD setup like Jenkins or Go CI.

Before you tin employ the CLI, yous'll need to plant a connection to a destination, that is, Google Play, App Shop, or Intune in the App Center. And compile a binary that works with your destination.

You can list your stores past using the list command like this:

              appcenter distribute stores listing \ --app {app_owner}/{app_name} \ --output json

You lot'll get a result like this:

              [["Alpha","googleplay","blastoff"],["Beta","googleplay","beta"],["Product","googleplay","production"]

And it'southward the Store cavalcade nosotros'll use in the final step.

The final step is to publish your app by running:

              appcenter distribute stores publish \ --file /path/to/file.aab \ --store Production \ --app {app_owner}/{app_name} \ --release-notes "Some annotation."

Yous'll need to make full in the blanks like the list command. Instead of having a static release note, it's possible to use the --release-notes-file instead. A release notation file is plain text file encoded with UTF-8.