发布到 TestFlight，新测试人员，我真的需要重建/下载我的配置文件吗？
我通过 testflight 网站发布了一个应用程序，让我的同事进行测试，随着越来越多的同事打开最初的电子邮件并抽出时间完成注册过程，测试人员逐渐加入我的 testflight 团队。
然而，将它们添加到测试中的过程似乎有点复杂，所以我想我应该验证一下，并询问我是否做得正确，或者是否遗漏了一些明显的东西。
目前，整个过程如下所示：
- 一位同事打开带有邀请链接的初始电子邮件，
- 然后他/她注册设备，并注册测试
- 我通过电子邮件和测试飞行网站获悉这位新测试员
- 然后，我必须下载（或记下/复制）自上次以来所有新测试仪的 UDID 列表，
- 然后我必须访问 Apple 开发人员网站的设备部分，并上传该文件
- 编辑我的配置文件以包含新的设备
- 等待它批准，并下载配置文件
- 我将配置文件拖到 Xcode 配置文件管理器中
- 然后返回 MonoDevelop，并确保它仍然指向正确的配置文件（我不知道使用 MonoDevelop/MonoTouch 是否会使情况复杂化）这个过程，所以我不想忽略它，它可能与这个问题无关）
- 我重建，并在 testflight 上重新发布，
- 然后访问 testflight 网站，找到新的/更新的版本，并确保所有我的测试人员被告知
我注意到，如果我不更新版本，它将“默默地”替换现有的版本，并重用已经通知的测试人员列表，所以如果我只是检查所有新的测试人员并完成，它只会通知新的。
然而，必须不断下载和处理配置文件文件似乎有点麻烦。
我错过了一些明显的事情吗？有没有办法让我变得更容易？
例如，我注意到我可以在 Xcode 管理器中创建一个配置文件，但是该对话框没有列出任何证书，因此我无法完成该对话框。如果这是一个关键要素，请对此效果留下一个简短的答案，我将重新发布一个有关该问题的新问题。
这个问题只是：上述过程正确吗？
I have published an app through the testflight website to allow my colleagues to test, and as more and more of them opens the initial email and find time to go through the registration process, testers are trickling in on my testflight team.
However, the process to add them to the test seems a bit convoluted, so I thought I'd verify, and ask, if I'm doing it right, or if I have missed something obvious.
At the moment the whole procedure looks like this:
- A colleague opens up the initial email, with the invitation link
- He/she then registers the device, and registers for the test
- I am informed of this new tester through an email and through the testflight site
- I then have to download (or write down/copy) the list of UDID's of all the new testers since last time
- I then have to visit the devices part of the Apple Developers site, and upload that file
- Edit my provisioning profile to include the new devices
- Wait for it to approve, and download the provisioning profile
- I drag the provisioning profile into the Xcode provisioning profile organizer
- I then go back to MonoDevelop, and ensure it is still pointing to the right profile (I don't know if using MonoDevelop/MonoTouch complicates this process so I didn't want to leave it out, it might be irrelevant for this question)
- I rebuild, and republish on testflight
- I then visit the testflight website, find the new/updated build, and ensure all my testers are informed of it
I noticed that if I do not update the version, it will "silently" replace the existing build, and reuse the list of testers that have already been informed, so if I just check all the new testers and complete, it'll only inform the new ones.
However, it seems a bit of a work to have to keep downloading and mucking about with the provisioning profile files.
Did I miss something obvious? Is there a way for me to make any part of this easier?
For instance, I noticed that I can create a provisioning profile inside the Xcode organizer, however that dialog box doesn't list any certificates so I can't complete that dialog. If this is a key element, leave a short answer to that effect and I'll instead repost a new question about that.
This question is just: Is the above procedure correct?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
无需重建 .ipa
希望有帮助。
No need to rebuild the .ipa
Hope that helps.
是的，您需要通过手动流程将 UDID 添加到您的个人资料中。不幸的是，没有办法解决这个问题。
创建新的规定后，如果您愿意，可以使用 xcode 来“同步”新的规定文件。打开它，转到管理器，选择左侧的“配置配置文件”，然后按刷新。老实说，我是手动完成的，毕竟这并不是什么工作。
Yes, you need to go thru that manual process to add UDIDs to your profile. There's no way around that, unfortunately.
After you create a new provision you can use xcode to "sync" the new provisions file if you would like. Open it up, go to the Organizer, select "Provisioning Profiles" on the left and press refresh. I honestly do it manually, it's not that much work after all.
Testflight 可以选择在几个月后更新您的配置文件。之前它就已经存在了，但需要启用“51区”功能才能看到它。
所以第 8、9 和 10 步不再需要了。
Testflight has an option to update your provisioning file since a couple of months. Before it was already there, but "Area 51" features should be enabled to see it.
So step 8, 9 and 10 are not needed anymore..
我已经为 iOS 上的 Ad-Hoc 应用程序做了相当多的工作，这就是 Apple 要求您采取的程序，除非您将订阅升级到企业帐户。
I've done quite a bit of work for Ad-Hoc applications on iOS and that's the procedure Apple makes you take unless you bump your subscription up to the Enterprise account.
TestFlight 过去允许上传新的配置文件，因此您无需重建即可添加新的测试人员。然后，TestFlight 将为您重新签名您现有的应用程序并相应地通知用户。但似乎在 Xcode 6 发布后，他们就取消了这个选项。可能与签署应用程序的新方式有关。
https://developer.apple.com/library/mac/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG205
TestFlight used to allow uploading of new provisioning profile so you didn't have to rebuild to add new testers. TestFlight would then re-sign your existing apps for you and notify users accordingly. But it seems after Xcode 6 came out, they took out that option. Probably has something to do with the new way of signing apps.
https://developer.apple.com/library/mac/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG205