iPhone：单个开发人员是否需要临时配置？
因此，我基本上使用开发人员配置文件来开发和测试我的应用程序。
现在我几乎准备好将我的应用程序提交到应用程序商店，并且我将使用应用程序商店配置文件。所以我真的不需要搞乱临时的，对吗？
（我认为这对于多个开发人员来说是某种巫毒魔法或其他什么？）
谢谢
So, I basically developed and tested my app using a developer provisioning profile.
now i'm almost ready to submit my app to the app-store, and I was going to use the app-store provisioning profile. so I don't really need to mess with the ad-hoc one at all right?
(I think it's some kind of voodoo magic for multiple developers or something?)
thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
如果您想与其他人一起进行进一步测试，您只需进行临时测试。与最终批准拨备基本相同。您最多有 100 个用户可以安装您的应用程序。
临时配置可帮助您进行比单个开发人员测试更大规模的测试。
测试人员总会找到一种方法来破坏您的应用程序，因此使用此步骤来帮助减少错误数量并顺利批准流程是一个很好的做法。
You only need ad-hoc if you want to test further with others. It is basically the same as the final approval provisioning. You have up to 100 users that can install your app.
Ad-hoc provisioning helps you test at a larger scale than your single developer test.
Testers will always find a way to break your app, so it is a good practice to use this step to help reduce your bug count and smooth your approval process.
Ad-Hoc 分发位于 App Store 之外。您必须使用批准用于分发和您的应用程序的配置配置文件来签署您的应用程序。也就是说，如果您指定应用程序 ID。如果您正在进行推送通知或应用内购买，则后者很常见。
Ad-Hoc distribution is outside the App Store. You must sign your app with the Provisioning Profile approved for Distribution and for you app. That is to say if you are specifying an App ID. That latter is common if you are doing Push Notifications or In App Purchases.
正如 Jason 所说，您需要完成配置过程才能将您的应用程序提交到 App Store。第一次这可能是一个乏味的过程 - 但您无法避免它。
也就是说，分发版本（非调试版本）是不同的可执行文件。因此，对它们进行这样的测试是有意义的。调试版本中不存在的问题不太可能突然在分发版本中显现出来 - 但这是可能的。
另外，除非您可以随意使用每台 iDevice 以及您所针对的 iOS 版本的每种组合，否则最好让其他人帮助确保不存在任何问题。
底线：如果没有首先在我的所有设备上部署 Ad Hoc 构建并与其他一些 iDevice 用户共享，我不会考虑将应用程序提交到 App Store。但是，YMMV。
As Jason said, you will need to go through the provisioning process in order to submit your app to the App Store. It can be a tedious process the first time - but you can't avoid it.
That said, Distribution builds (non-Debug builds) are different executables. So, it makes sense to test them as such. It is unlikely that problems that were absent in the Debug build will suddenly manifest themselves in the Distribution build - but it's possible.
Also, unless you have at your disposal every iDevice with every combination of iOS releases that you are targeting, then it's nice to have others help make sure that there are no gotchas.
Bottom line: I wouldn't consider submitting an app to the App Store without first deploying Ad Hoc an build on all my devices and sharing it with a few other iDevice users. But, YMMV.
不，没有必要。 :)
No, it's not necessary. :)