xcode Apple 的 TestFlight 提供旧版本
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/27122771/
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
Apple's TestFlight provides old builds
提问by Benjohn
My team uses TestFlight to deploy beta builds within the company. Frequently, the TestFlight App does not want to install the latest version.
我的团队使用 TestFlight 在公司内部部署测试版。通常，TestFlight 应用程序不想安装最新版本。
For example, we will get a TestFlight email informing us about an App update for build #91. The email includes a link ""Open in TestFlight". When you tap the link, TestFlight opens, but offers to install build #90(an older build), instead of build #91(the latest).
例如，我们将收到一封 TestFlight 电子邮件，通知我们有关build #91的应用程序更新。该电子邮件包含一个链接““在 TestFlight 中打开”。当您点击该链接时，TestFlight 会打开，但会提供安装版本 #90 （旧版本），而不是版本 #91 （最新版本）。
- Is this a known problem?
- Are there work arounds to improve the situation?
- 这是一个已知问题吗？
- 是否有解决方法来改善这种情况？
回答by Quver
In the "Prereleases" list for your App, once your build has finished processing, you'll be able to click the link for that particular test build and go a page with meta data about it. Switch to the "Test Information" tab.
在您的应用程序的“预发布”列表中，一旦您的构建完成处理，您将能够单击该特定测试构建的链接并转到包含有关它的元数据的页面。切换到“测试信息”选项卡。
I had filled "TestFlight Beta Information" section, but empty "Beta App Review Information". After filled second one and saved, I received email and notification about new build available.
我填写了“TestFlight Beta Information”部分，但空白“Beta App Review Information”。填写第二个并保存后，我收到了有关新版本可用的电子邮件和通知。
Solution:
解决方案：
Fill whole form:P
填写完整表格:P
回答by Unar
I must emphasize that currently, there are 2 ways to force iTunes Connect to push the update out:
我必须强调，目前有两种方法可以强制 iTunes Connect 推送更新：
1) Enter meta data and update the build.
1) 输入元数据并更新构建。
2) Disable TestFlight Beta Testing, and re-Enable it.
2) 禁用 TestFlight Beta 测试，然后重新启用它。
But these are both workarounds; internal testing is not supposed to work this way.
但这些都是解决方法；内部测试不应该以这种方式工作。
I have attempted to file a bug report to Apple Support as detailed in another post: https://stackoverflow.com/a/27197057/4305185
我已尝试向 Apple 支持提交错误报告，详见另一篇文章：https: //stackoverflow.com/a/27197057/4305185
I suggest you guys try the same; more reports means more chance of them actually seeing one of them.
我建议你们也试试；更多的报告意味着他们有更多机会真正看到其中的一个。
回答by Benjohn
Lots of helpful answers here – thank you everyone.
这里有很多有用的答案——谢谢大家。
I just noticed something interesting.
我刚刚注意到一些有趣的事情。
I set up the "What to test" info beforethe new build had finished being in the "Processing" state (the other info is copied over for a new build). When it completed processing, no messages were sent.
我在新构建完成处于“处理”状态之前设置了“要测试的内容”信息（其他信息被复制以用于新构建）。当它完成处理时，没有发送任何消息。
I went back to the build info and changed "What to test" enough to enable a Save. On hitting Save, the TestFlight notifications were immediatelysent to the test devices I have (and I assume to my colleagues' too).
我回到构建信息并更改了“测试内容”以启用保存。点击“保存”后，TestFlight 通知会立即发送到我拥有的测试设备（我也假设给我同事的）。
On this build I have the "What to Test", "App Description" and "Feedback Email" fields set, but I have left the other fields blank.
在此版本中，我设置了“要测试的内容”、“应用程序说明”和“反馈电子邮件”字段，但我将其他字段留空。
I suspect that any save operationin this form after the build finishes "Processing"is enough to fire off the update emails. If you fill in everything, it takes you longer, and you are more likely to press Saveonce "Processing" has finished :-)
我怀疑在构建完成“处理”后任何以这种形式进行的保存操作都足以触发更新电子邮件。如果您填写所有内容，则需要更长的时间，并且Save一旦“处理”完成，您更有可能按下:-)
回答by Alwin
I was getting same problem but was able to fix it. I went to the meta data section of new build and added added some text and did a save. And now my build became active and the emails were sent to internal testers.
我遇到了同样的问题，但能够解决它。我去了新版本的元数据部分并添加了一些文本并进行了保存。现在我的构建变得活跃，电子邮件被发送给内部测试人员。
