Once an app has been released, we will want to provide additional features or fix any bugs. We can easily do this by uploading a later version of our app to Google Play.
When we want to update an app, we will need to ensure that our new app will have the same package name and can be signed by the same keystore.
Releasing updates to an existing app on Google Play is straightforward, only requiring that the version numbers be increased besides any code changes:
- The Version number field needs to be a greater integer value than the current release, and the Version name field should be a higher semantic version:
Increasing the app version numbers
- Next, we must archive and sign the app package in the same manner as with the previous release.
- Then, we go to the APK section in the dashboard of the app we want to update. On the Alpha tab, click on the Upload new APK to Alpha button.
- In the dialog that appears, browse to and select the APK that we just packaged using our IDE.
The upload new APK dialog
- Once the upload is complete, enter any release notes before clicking on the Publish now to Alpha button:
The upload new APK dialog
App updates are very important, as they let the user know that we are still supporting them, especially if this was a paid app. The actual release process is just the package and upload steps. We do not have to create a new store listing or new keystores.
Once the app update has been developed, we just package and sign the app. We must ensure that the package name is the same as the previous version, the version numbers have been increased, and the final package is signed with the same key.
When the package is created, we then go ahead and upload the new package to any one of the channels. Usually, we would want to upload to a testing channel so that the new package can be tested before the final release.
Testing updates is important as we may have an app with a high rating, but a poor update can result in a drop in the ratings. Also, testing an app with a few users allows us to make changes before the app goes to production and to the rest of the users.