This article explains how to manually update your published Android app in the Google Play Store using the .APK file obtained via the Google Play publishing process in AppMachine.
Note that the file downloaded from AppMachine is a .zip file. This .zip file contains the following files:
- APK / AAB
- App icon
- Feature image
- Screenshots
Extract the .APK file (or .AAB file, starting August 2, 2021) from the .zip file, and upload the .APK or .AAB file to Google when required. Attempting to upload the .zip file to Google will result in an error.
Updating an already published app in the Google Play Store is a lot less time consuming than publishing an app for the first time. When submitting an app for the first time, all store data has to be provided to Google. When updating an existing app, you only have to update the item(s) that you wish to change.
To update your app in the Google Play Store we'll be focusing on the 'Store presence', 'App content', and 'Release management' sections. The app itself can be updated via a new release (APK file), and the information displayed in the Google Play Store, on the download page of your app, is known as the store presence.
Store presence.
After opening your app from the 'All apps' page, the store presence section can be found in the left-side menu of your Google Play developer console. Within the store presence section, there are multiple pages on which the app's presence in the Google Play Store can be edited. Within this article, and to keep things simple, we'll focus on the following:
- Main store listing.
- The main store listing allows you to edit the title, descriptions, icon, feature graphic and screenshots of your app. This is the main display of your app in the Google Play Store.
- The main store listing allows you to edit the title, descriptions, icon, feature graphic and screenshots of your app. This is the main display of your app in the Google Play Store.
- Store settings.
- The store settings allows you to edit the type and category of your app, as well as the contact details displayed on the download page of your app in the Google Play Store.
If you've made any changes on these pages, use the Save button in the bottom-right corner of the screen to save your changes.
App content.
All the way at the bottom of the left-side menu of your Google Play developer console, you will find the Policy section from which the App content page can be opened.
On the App content page, make sure that all options are marked as 'Completed'. If there are any open tasks in the To-do list (Google adds new things from time to time), then you will have to make sure to complete these tasks before submitting a new version of your app to the Google Play Store.
On this page you will be able to edit the following information:
- App access.
- If parts of your app are restricted based on login credentials, memberships, location, or other forms of authentication, you will have to provide Google with instructions on how to access them via this section.
- If parts of your app are restricted based on login credentials, memberships, location, or other forms of authentication, you will have to provide Google with instructions on how to access them via this section.
- Privacy policy.
- You can add or edit your app's privacy policy via this section.
- You can add or edit your app's privacy policy via this section.
- Ads.
- If your app contains ads, then you can let Google know about this via this section.
- If your app contains ads, then you can let Google know about this via this section.
- Content ratings.
- You can view and edit your app's current IARC rating via this section.
- You can view and edit your app's current IARC rating via this section.
- Target audience and content.
- You can view and edit your app's current target age group, and other content information via this section.
- You can view and edit your app's current target age group, and other content information via this section.
- News apps.
- If your app is a news app, then you'll have to provide Google with additional information to help them verify your credentials as a news publisher. Furthermore, your app will have to comply with the Google Play News Policy. If your app is not a news app, then a simple 'No' will suffice.
- Sensitive app permissions.
- If your app requests access to sensitive permissions, like location permissions, you need to tell Google what functions the permission is used for. (more information below)
- If your app requests access to sensitive permissions, like location permissions, you need to tell Google what functions the permission is used for. (more information below)
Sensitive app permissions.
Scroll all the way to the bottom of the left-side menu of your developer console. At the bottom you will find a Policy submenu in which 'App content' is listed. Open the 'App content' page and click the 'Start' button below the Sensitive app permissions setting.
The next page is titled 'Permission declaration form'. Hit the 'start' button below the 'Location permissions' to provide the required information.
Next you'll be presented with a question regarding the background use of the location permission. This question can be answered with 'No'.
Use the Save button in the bottom-right corner of the screen to save your changes and to complete the permission declaration form.
Data safety.
Scroll all the way to the bottom of the left-side menu of your developer console. At the bottom you will find a Policy submenu in which 'App content' is listed. Open the 'App content' page and click the 'Start' button below the Data safety setting.
Release management.
Within the Release section of the left-side menu, you'll find the Production option. Opening this page will allow you to create a new release and roll it out to production.
To create a new release, use the 'Create new release' button in the top-right corner of the Production page.
If you haven't set the App signing by Google Play option yet, then use the Manage preferences button and choose the option to 'Let Google manage and protect your app signing key (recommended)’.
Unzip the package you've downloaded from the Publish page in AppMachine, which contains your app's APK or AAB file. Upload the APK or AAB file to Google by either dragging and dropping it onto the screen, or by using the Upload button displayed on the page.
A name for the release will automatically be filled in. Optionally, you can enter release notes for this version to inform your app users about the changes within this new version of the app.
Use the Save button in the bottom-right corner of the screen to save your changes. After saving the changes, use the Review release button. Review the new version and use the 'Start rollout to Production' button to release the app into the Google Play Store.
In case the app is rejected -or suspended as Google calls it- you will receive an email notification from Google on the owner email address of your Google Play developer account explaining why the app was suspended and what needs to be changed.
The time it takes Google to review is generally anywhere between 2-7 days, depending on the amount of apps that have been submitted to Google.
Congratulations, you've successfully updated your Android app in the Google Play Store!