问题描述
我的意思是:如果 beta 说 v2.2.4 build 1234 被证明是好的，并且会进入 App Store(这意味着最终发布版本将是相同的(v2.2.4 build 1234).beta 测试人员会能够更新"到 App Store 版本(具有相同的版本/构建号)以避免他们的应用在 30 天后(testflight beta 有效期结束时)变得无法使用?
I mean: if beta say v2.2.4 build 1234 proves to be good, and will make its way to the App Store (this means the final release version will be the same (v2.2.4 build 1234). Will beta testers be able to "update" to the App Store version (which has the same version/build no.) to avoid their app become unusable after 30 days (when testflight beta validity ends)?
或者，在生产版本上使用上次成功测试中使用的相同版本/内部版本号是否明智?
Or, is it even wise to use the same version/build number used in the last successful beta on the production version?
推荐答案
简短回答:是
为生产版本使用相同的测试版是完全没问题的.我们一直这样做.版本号不会有问题，实际上是推荐的.
It's perfectly fine to use the same beta build for production version. We do that all the time. Version number won't be an issue, in fact it is recommended.
用户将能够通过从 App Store 下载来下载/更新到 App Store 版本，甚至可以通过从 Testflight 再次下载它来返回测试版本.
The users will be able to download/update to App store version by downloading from App Store and can even go back to the beta build by again downloading it from Testflight.
这篇关于iTunesConnect (Testflight) 预发布测试结束.该应用程序转到 App Store.它可以具有与测试版相同的版本号吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！