如何控制 Google Play Console 上的应用版本？
我们有一个尚未上市的应用程序，我们正在努力开发测试人员下载的测试版本。我们正在尝试设置 v1.0.1，但 Google Play 将它们重定向到不是最新的 v1.0.0。我们甚至尝试停用该分支，但问题仍然存在。
we've got an app that's not on the market yet and we are struggling with the testing version that testers download. We're trying to set the v1.0.1 but Google Play redirects them to v1.0.0 which is not up to date. We even tried to deactivate that branch but the issue still insists.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我为多个测试组做了很多测试部署。
Google 支持 3 种不同类型的测试组：开放、封闭、内部。
开放测试实际上对任何想要选择加入的人开放，他们可以通过您可以从开发者控制台复制的链接加入。开放测试要求应用程序在推出之前经过审查。
封闭式测试与开放式测试类似，但您可以通过电子邮件地址列表明确定义谁有权访问。封闭测试在推出之前还必须通过基本的 Google 审核。
内部测试与封闭测试类似，但它从不经过审核过程。同样，这是通过电子邮件地址列表控制的。
我经常发布不同的版本，其中Internal 拥有最新的前沿技术。
您没有说明您正在使用哪个渠道（开放、封闭、内部），但我会仔细查看每个渠道以及关联的电子邮件地址。然后我会点击控制台上的发布概述按钮来查看是否还有尚未完成的内容。
I do a lot of test deployments for multiple test groups.
Google supports 3 separate types of test groups: Open, Closed, Internal.
Open Testing is literally open to anyone who wants to opt in and they can join via a link you can copy from the developer console. Open testing requires the app go thru review before being rolled out.
Closed Testing is similar to Open but you explicitly define who has access with a list of email addresses. Closed testing must also pass through a basic Google review before being rolled out.
Internal Testing is similar to Closed testing but it never goes through a review process. Again, this is controlled via a list of email addresses.
I routinely publish different versions where Internal has the latest bleeding edge.
You don't state which channel you are using (Open, Closed, Internal), but I would carefully review each channel and the email addresses associated. Then I would click on the Publishing Overview button on the console to see if there's something you haven't finished.