ios 在 TestFlight Beta 的测试期结束后，构建状态更改为 Expired
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/31555382/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
After the testing period has ended for a TestFlight Beta, the build status changes to Expired
提问by soumya
In Apple's iTunes Connect Developer Guide, Apple has stated:
在 Apple 的iTunes Connect Developer Guide 中，Apple 声明：
- When a build has Active status, the number of days remaining for testing is shown.
- After the 30 day testing period has ended, the build status changes to Expired.
- Builds not currently being tested will have the status Inactive.
- 当构建处于活动状态时，将显示剩余的测试天数。
- 30 天测试期结束后，构建状态更改为已过期。
- 当前未测试的构建将处于非活动状态。
Can anyone please tell me what does this means?
谁能告诉我这是什么意思？
Whether the TestFlight Beta is not available for new testers to install the app
When the testing period ends, testers that already have builds installed will not be affected
TestFlight Beta 是否不适用于新测试人员安装应用程序
测试期结束时， 已经安装了构建的测试人员不会受到影响
My test beta app is expired. Can my testers continue testing the build that's already installed on their devices, or should I upload a new build?
我的测试版应用程序已过期。我的测试人员可以继续测试他们设备上已经安装的构建，还是应该上传一个新的构建？
I looked at this previous SO post, but it didn't help.
我查看了之前的 SO post，但没有帮助。
Thank you!
谢谢！
I found the solution here:
我在这里找到了解决方案：
This is a general limitation when using TestFlight. Apple probably wants to prevent that TestFlight can be used to distribute Apps to users outside of the App Store, so they enforce a strict expiry policy. The App runs for 30 days and will then stop working.You can update your beta within this 30 day period, so beta testers can update and then get again 30 days. The 30-day limit is documented by Apple and also the TestFlight App will tell the user about this limit. If you think this is not enough, you should tell your beta testers about it as well.
The alternative would be to go the "old way" by distributing your App via iTunes with AdHoc provisioning profiles. This way you need to register the UDIDs for each device yourself, you are limited to 100 devices in total, but the beta will run until the provisioning profile expires (AFAIK these profiles needs to be renewed every year).
这是使用 TestFlight 时的一般限制。Apple 可能希望防止 TestFlight 可用于向 App Store 以外的用户分发应用程序，因此他们实施了严格的到期政策。该应用程序运行 30 天，然后将停止工作。您可以在这 30 天内更新您的 Beta 版，因此 Beta 版测试人员可以更新，然后再获得 30 天。Apple 记录了 30 天的限制，TestFlight 应用程序也会告诉用户这个限制。如果您认为这还不够，您也应该告诉您的 Beta 测试人员。
另一种方法是走“老路”，通过带有 AdHoc 配置文件的 iTunes 分发您的应用程序。通过这种方式，您需要自己为每个设备注册 UDID，总共限制为 100 个设备，但测试版将一直运行到配置文件过期（AFAIK 这些配置文件需要每年更新）。
EDIT:The beta period used to be 30 days, but has been increased to 90 days.
编辑：测试期过去是 30 天，但已增加到 90 天。
采纳答案by Michael Dautermann
Your TestFlight app users should not be able to launch the app 90 days after you release itdue to provisioning limitations.
由于配置限制，您的 TestFlight 应用程序用户应该无法在您发布应用程序 90 天后启动该应用程序。
If you want your test versions to last beyond 90 days, you can use good old fashioned ADHOC builds(but you'll be limited to 100 users versus the 10,000 you can use via TestFlight).
如果您希望您的测试版本持续超过 90 天，您可以使用良好的老式ADHOC 构建（但您将被限制为 100 个用户，而您可以通过 TestFlight 使用 10,000 个）。
回答by Karl Nosworthy
If you have a tag/access to the code of the build that has expired, a simple bump of the version number and a reissue to iTunes Connect makes the build immediately available for another 60 days.
如果您拥有已过期版本代码的标签/访问权限，只需简单地修改版本号并重新发布到 iTunes Connect 即可让该版本在 60 天内立即可用。
I had this problem this morning but needed to keep the groups and try to get a build out as cleanly as possible and so that worked a treat.
今天早上我遇到了这个问题，但需要保持团队并尝试尽可能干净地进行构建，这样就可以了。
