Stay organized with collections
Save and categorize content based on your preferences.
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 on PC version available
Google Play Games on PC requires you to maintain the availability of Google Play Games on PC
versions along with mobile versions. This requirement includes the following
scenarios:
Verify Google Play Games on PC 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 on PC 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 on PC version.
The link on Google Play Games on PC 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 on PC and then use
the correct link.
Pre-submit checklist
This section describes a checklist that you need to verify before you submit each
update.
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 google-play-games-support@google.com
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 on PC
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 on PC requirements.
Content and code samples on this page are subject to the licenses described in the Content License. Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.
Last updated 2024-09-19 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-09-19 UTC."],[],[],null,["# Update your game\n\nThis guide describes how to update your game after it has been approved to\nupload to the production track. It lists items to verify before updating your\ngame and publishing tasks to perform on new versions.\n\nKeep the Google Play Games on PC version available\n--------------------------------------------------\n\nGoogle Play Games on PC requires you to maintain the availability of Google Play Games on PC\nversions along with mobile versions. This requirement includes the following\nscenarios:\n\n- Verify Google Play Games on PC version after you update the mobile\n version or related configurations on the server side.\n\n A common mistake in this scenario is that developers forget to verify\n their Google Play Games on PC version after they update the mobile version\n and/or server's configurations, which causes the server to reject requests for\n the outdated Google Play Games on PC version.\n- Use the [link to Google Play](/distribute/marketing-tools/linking-to-google-play#OpeningDetails)\n for downloading a new update.\n\n The link on Google Play Games on PC is the same as on mobile. A common\n mistake in this scenario is that developers use a different link for\n mobile when they detect the game is running in an emulator. You can\n [detect Google Play Games on PC](/games/playgames/%22pc-compatibility#detect-hpe) and then use\n the correct link.\n\nPre-submit checklist\n--------------------\n\nThis section describes a checklist that you need to verify before you submit each\nupdate.\n\n### Mobile checklist\n\n- [Evaluate your game against the continuity requirements](/games/playgames/continuity-expected-behaviors).\n\n### Google Play Games on PC checklist\n\n- New features are shipped simultaneously with the mobile version.\n- Verify the [Google Play Games on PC requirements checklist](/games/playgames/start#requirements-checklist).\n\nPublishing flows\n----------------\n\nWe highly recommend that you always put a release candidate build on the test\ntrack for game updates as soon as it's available. Contact **google-play-games-support@google.com**\nwith your package name and version code to request a review.\n\n\n**Figure 1.** Recommended publishing flow for review requests on the test track.\n\nIn figure 1, there are 4 phases:\n\n1. Development phase. This includes coding, debugging, and testing.\n\n2. Checklist phase. This includes verifying mobile and Google Play Games on PC\n checklists.\n\n3. Publishing phase. Uploads versions to the test track before the production\n track, and then requests a review for the test track.\n\n4. Review phase. This is performed in parallel with production publishing.\n\nThe other option is to request a review for the production track directly if\nyou are in an emergency situation, such as your game experiencing a crash that\nmust be fixed as soon as possible.\n\n\n**Figure 2.** Recommended publishing flow for making review requests directly\non the production track.\n\nIn figure 2, there are also 4 phases. The development and checklist phases are\nthe same as figure 1. In the publishing phase, you are able to upload to the\nproduction track directly and the requested review is performed after\npublishing.\n\nFor both publishing flows, we will contact you if we find violations of the\nGoogle Play Games on PC requirements."]]
Figure 1. Recommended publishing flow for review requests on the test track.
Figure 2. Recommended publishing flow for making review requests directly
on the production track.