我在Google Play商店中有一个制作应用程序。我还使用Google Play测试版功能向有限组发布了测试版。但是，如果我对生产应用程序进行更改，则需要重新构建并重新发布测试版应用程序，因为它会被新的生产版本覆盖。当我想在不改变测试版的情况下对生产进行一些错误修复时，这非常令人沮丧。有没有什么方法可以在不使目前的测试版失效的情况下发布新的产品应用程序？解析方案
基本问题是Google Play更新基于（ versionCode ），并且不关心.apk来自哪个频道。
您的唯一选项不是取代顺序构建号码，而是留下空白。例如，如果您的产品版本是 versionCode =10，请使beta版本 versionCode =20您在发布无效测试版之前可以发布9个以上的小版本。
尽管这种方法存在两个问题：
- 显然它不能很好地扩展。
- 这使得难以管理构建编号，因为现在您必须记录构建已达到哪个构建编号的记录。
- 如果您没有使测试版本无效，那么您的测试版用户仍然会在新版本中修复错误，直到升级为止。
请注意，如果您没有阻止自动升级的权限更改，则使测试版本无效并发布新版本并不是什么大问题;大多数用户甚至不会注意到他们已升级（除非您的应用程序明确告诉他们）。
I have a production app on the Google Play store. I have also released a beta version to a limited group using the Google Play beta feature. However, if I make changes to the production app, I then need to re-build and re-release the beta app because it gets overwritten by the new production version. This is very frustrating when I want to make some bug fixes on production without changing the beta. Is there any way to release a new production app without invalidating the current beta?
The basic problem is that Google Play updates based on build number (versionCode), and doesn't care which channel the .apk comes from.
Your only option is to not pickup sequential build numbers, but instead leave gaps. For example if your prod is versionCode="10", make the beta build versionCode="20" which will give you the chance to publish nine more minor prod releases before you hit the issue of invalidating the beta build.
Though there are two problems with this approach: - Obviously it does not scale very well. - It makes it hard to manage the build numbers, as now you have to keep a record of what build has reached which build number. - If you don't invalidate the beta build, your beta users will still have the bugs you just fixed in the new prod build until you upgrade them.
Note that if you don't have permission changes that prevent auto-upgrade, invalidating the beta build and publishing a new one is not that much of an issue; most users won't even notice that they were upgraded (unless your app tells them explicitly).
这篇关于在Google Play上发布新的制作版本，而不会影响测试版的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！