更新游戏
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
本指南介绍了在游戏获得批准上传到正式版轨道后，如何对其进行更新。其中列出了在更新游戏和发布针对新版本执行的任务之前要验证的内容。
保持 Google Play 游戏电脑版的可用性
Google Play 游戏电脑版要求您同时保持 Google Play 游戏电脑版和移动版的可用性。此要求包括以下几种情形：
在更新移动版或服务器端的相关配置后，验证 Google Play 游戏电脑版。
此情形的一个常见错误是，开发者在更新移动版和/或服务器配置后忘记验证其 Google Play 游戏电脑版，这会导致服务器拒绝针对过时 Google Play 游戏电脑版所发出的请求。
使用 Google Play 链接下载新的更新。
Google Play 游戏电脑版上的链接与移动版上的链接相同。此情形的一个常见错误是，开发者在检测到游戏在模拟器中运行时，针对移动版使用了不同的链接。您可以检测 Google Play 游戏电脑版，然后使用正确的链接。
提交前核对清单
本部分介绍了您在提交每次更新之前需要验证的核对清单。
移动版核对清单
Google Play 游戏电脑版核对清单
发布流程
我们强烈建议您始终在有游戏更新时尽快将候选版本 build 纳入测试轨道。如需请求审核，请发送电子邮件至 google-play-games-support@google.com，并附上您的软件包名称和版本代码。
图 1. 测试轨道审核请求的建议发布流程。
图 1 中有 4 个阶段：
开发阶段。其中包括编码、调试和测试。
核对清单阶段。其中包括验证移动版和 Google Play 游戏电脑版核对清单。
发布阶段。将版本上传到正式版轨道之前先上传到测试轨道，然后请求对测试轨道进行审核。
审核阶段。此步骤与正式版发布步骤同时执行。
另一种方法是在紧急情况下（例如游戏遇到崩溃问题，且必须尽快解决）直接申请对正式版轨道进行审核。
图 2. 在正式版轨道上直接提出审核请求的建议发布流程。
图 2 中也有 4 个阶段。其中开发和核对清单阶段与图 1 相同。在发布阶段，您可以直接上传到正式版轨道，已请求的审核会在发布之后执行。
如果在上述两个发布流程中发现有违反 Google Play 游戏电脑版要求的行为，我们将与您联系。
本页面上的内容和代码示例受内容许可部分所述许可的限制。Java 和 OpenJDK 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-07-27。
[null,null,["最后更新时间 (UTC)：2025-07-27。"],[],[],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."]]
