This guide describes how to update your game after it has been approved to upload to the production track. It lists items to verify before updating your game and publishing tasks to perform on new versions.
Keep the Google Play Games version available
Google Play Games requires you to maintain the availability of Google Play Games versions along with mobile versions. This requirement includes the following scenarios:
Verify Google Play Games version after you update the mobile version or related configurations on the server side.
A common mistake in this scenario is that developers forget to verify their Google Play Games version after they update the mobile version and/or server's configurations, which causes the server to reject requests for the outdated Google Play Games version.
Use the link to Google Play for downloading a new update.
The link on Google Play Games is the same as on mobile. A common mistake in this scenario is that developers use a different link for mobile when they detect the game is running in an emulator. You can detect Google Play Games and then use the correct link.
This section describes a checklist that you need to verify before you submit each update.
Google Play Games checklist
- New features are shipped simultaneously with the mobile version.
- Verify the Google Play Gamesrequirements checklist.
We highly recommend that you always put a release candidate build on the test track for game updates as soon as it's available. Contact firstname.lastname@example.org with your package name and version code to request a review.
Figure 1. Recommended publishing flow for review requests on the test track.
In figure 1, there are 4 phases:
Development phase. This includes coding, debugging, and testing.
Checklist phase. This includes verifying mobile and Google Play Games checklists.
Publishing phase. Uploads versions to the test track before the production track, and then requests a review for the test track.
Review phase. This is performed in parallel with production publishing.
The other option is to request a review for the production track directly if you are in an emergency situation, such as your game experiencing a crash that must be fixed as soon as possible.
Figure 2. Recommended publishing flow for making review requests directly on the production track.
In figure 2, there are also 4 phases. The development and checklist phases are the same as figure 1. In the publishing phase, you are able to upload to the production track directly and the requested review is performed after publishing.
For both publishing flows, we will contact you if we find violations of the Google Play Games requirements.