In February 2023, we made changes to your publishing workflow to make it easier to understand which changes you're sending for review. You can also better control when you send certain changes for review.Visit the Android Developers Blog to learn more.
With a release, you can manage your app's Android App Bundle (or APK for apps created before August 2021) and then roll out your app to a specific track.
A release is a combination of one or more app versions that you'll prepare to launch an app or roll out an app update. You can create a release on three different testing tracks or to production:
- Open testing: Open testing releases are available to testers on Google Play. Users can join tests from your store listing.
- Closed testing: Closed testing releases are available to a limited number of testers that you choose, who can test a pre-release version of your app and submit feedback.
- Internal testing: Internal testing releases are available to up to 100 testers that you choose.
- Production: Production releases are available to all Google Play users in your chosen countries.
- You must have the Release apps to testing tracks permission to create a new release.
- Developers with personal accounts created after November 13, 2023, must meet specific testing requirements before they can make their app available on Google Play. Read this Help Center article to learn more.
To start your release:
- Open Play Console and go to the track you want to start your release on:
- Near the top right of the page, click Create new release.
- Note: If Create new release is disabled, you may have outstanding setup tasks to complete. These may be listed on the Dashboard page.
If you want to edit an existing release, you can go to the appropriate release page as listed in step 1 above, and click Edit release.
Tip: For more information on testing, go to set up an open, closed, or internal test.
- Follow the on-screen instructions to prepare your release:
- If this is your first release for this app, follow the instructions to configure Play App Signing.
- Add your app bundles.
- Note: Apps created before August 2021 can add app bundles or APKs for app updates.
- Optional: If this is the first time you’re creating a release, you have the option to change your app signing key. In the "App integrity" section, click Change app signing key. Before changing your key, understand that:
- Internal and closed track users who already installed your app will no longer receive updates. These users will need to uninstall and reinstall the app to receive updates.
- You will not be able to use any previously uploaded app versions. You will need to re-upload app versions.
- Name your release.
- Enter release notes.
- For more information on any of these fields, select the matching section heading under “Prepare” below.
- To save any changes you make to your release, select Save as draft.
- When you've finished preparing your release, select Next.
Note: Once you publish an app to an open track, its key is fixed.
Select a section heading below for more information.App integrity
This section shows the status of Play App Signing. Learn more about using Play App Signing.
In this section, you can upload new app bundles or add them from your library. You can also click the three dots icon to:
- upload a ReTrace mapping file (.txt)
- upload native debug symbols (.zip)
- upload an expansion file (.obb)
- remove an app bundle
Note: Apps created before August 2021 can use app bundles or APKs in releases.
To learn more about why you would upload ReTrace Mapping files and native debug symbols, go to Deobfuscate crash stack traces.
In this section, view details about app bundles from your previous release that will be included in this release.
Clicking Remove will remove the app bundle from this release. You can find the app bundle or APK again in your App bundle explorer.
In this section, view details about app bundles from your previous release that will not be included in this release.
Clicking Include will add the app bundle to this release.
Permission requests are evaluated during the release process after adding your app bundles or APKs. If your app requests the use of high-risk or sensitive permissions (for example, SMS or Call Log), you may be required to complete the Permissions Declaration Form and receive approval from Google Play.
The release name is only for use in Play Console and won't be visible to users.
We'll auto-populate the field with the version name of the first app bundle or APK added to the release.
To make your release easier to identify, add a release name that's meaningful to you, like the build version ("3.2.5-RC2") or an internal code name ("Banana").
Let your users know about recent updates that you've made in this release of your app. Release notes shouldn't be used for promotional purposes or to solicit actions from your users.
Add release notes and manage translations
Add the description for your app's release between the relevant language tags. Language tags will be shown in the text box for each language your app supports.
To change your app's supported languages, you must first add translations. When you return to the Prepare release page, the latest set of languages will be shown in the text box.
When entering text, make sure the language tags are on separate lines from the release notes. The format should match the following:
The release notes description can take up multiple lines.
Note: You can enter release notes using up to 500 Unicode characters per language.
Copy from previous release
To copy release notes from a previous release, select Copy from a previous release. On the next screen, selecting a release will copy the release notes and any translations into the text box for further editing. This will replace any existing release notes that you may have entered.
Important: When preparing your release, you may have the option to Save or Publish depending on whether or not the changes you made to your app need to be reviewed. Publishing will push your changes live immediately. Saving your changes will add them to the "Changes ready to send for review" on the Publishing overview page, where you can decide when you want to send the changes for review. Learn more about managing when changes go live.
Once you're ready to roll out your app:
- Open Play Console and go to the Releases Overview page.
- Next to the release you want to roll out, select the right arrow to open the Release details page.
- Tip: Use the search bar if you can’t find your release.
- In the “Release overview” section, select View release dashboard.
- Select the Releases tab, then Edit.
- Review your draft release, make any necessary additional changes, and select Next. You'll be taken to the "Preview and confirm" screen, where you can make sure there aren't any issues with your release before rolling it out to users.
- If you see the heading “Errors summary” at the top of the page, click Show more to review the details and resolve any problems.
- Note: When available, you can also view the recommended or required resolution. You can’t publish your app until errors have been resolved. If you only have warnings, minor issues, or a combination of the two, then you can still publish your app, but we recommend addressing them before publishing.
- If you're updating an existing app, select a rollout percentage.
- If you're rolling out your first release, you won't see the option to select a rollout percentage.
- For details on how to target a staged rollout to specific countries, go to release app updates with staged rollouts.
- Select Start rollout.
- If you're rolling out your app's first release on production, clicking Start rollout to production will also publish your app to all Google Play users in the countries you selected.
Step 4: Review release details
Once you've created a release, you'll see the following information for the latest app release you rolled out to each track in a table under “Latest releases” on your Releases overview page.
- Release: Name to identify release in Play Console only, such as an internal code name or build version.
- Track: The track that the release has been rolled out to.
- Release status: The current status of your release.
- Last updated: A date and timestamp indicating the last rollout event for your release.
- Countries/regions: The number of countries/regions the last rollout of your release is available to. After you roll your app release to Production, Open testing, or a Closed testing track, you can target your release in each track to users in specific countries. Read this article to understand how to manage your app's availability in different countries/regions.
You can view more in-depth information by selecting the right arrow to open the release’s Release details page, which includes:
- Release overview: A set of metrics relating to your app's number of installs and updates, performance issues, and rating measured against previous releases.
- App bundles and APKs: A list of new, retained, and deactivated app bundles and APKs associated with your release.
- Release notes: A list of previous release notes.
- Rollout history: A timeline that shows timestamps for when your app's release was halted, resumed, or served to a new percentage of users.
If you’ve rolled out multiple releases, the Releases overview page (under “Release” in the left menu) helps you stay on top of all releases in one place. It’s a single location where you can monitor the availability of your apps across different tracks, view the countries/regions it’s available in, and select individual releases to view their specific details.
- Discover more information on managing country availability across your app's production, open, and closed releases in Distribute app releases to specific countries.
- Get more information about testing in Set up an open, closed, or internal test.
- Learn more about releasing updates progressively with staged rollouts in the Academy for App Success.