为什么不使用开发配置而不是临时配置？
我的印象是，当您使用开发配置文件来构建应用程序时，只有指定的开发人员才能将该构建部署到手机上。
但我刚刚使用 Xcode Organizer 将使用开发配置文件的构建部署到手机上，尽管我不是该配置文件的有效开发人员之一。我的一位同事甚至没有安装 Xcode，但他使用 iTunes 对他的手机做了同样的事情。
在这种情况下，为什么不使用开发配置文件将您的应用程序分发给例如您的 QA 团队，而不是使用临时分发？
编辑：请在回答之前仔细阅读粗体部分。我不是在问一个基本的“这是如何工作的”问题。我已经进行了大量的开发、临时和应用程序商店构建，现在我发现我似乎做出了一些错误的假设。
I was under the impression that when you use a development provisioning profile for a build of an app, only the specified developers can deploy that build to a phone.
But I just deployed a build that uses a development profile to a phone using Xcode Organizer, even though I'm not one of the valid developers for that profile. One of my colleagues, who doesn't even have Xcode installed, did the same with his phone using iTunes.
In that case, why not use a development provisioning profile for distributing your app to e.g. your QA team, instead of ad hoc distribution?
EDIT: Please read the part in bold carefully before answering. I'm not asking a basic "how does this work" question. I've made a lot of development, ad hoc, and app store builds, and now I find that I seem to have made some wrong assumptions.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
在一种情况下，您需要临时配置文件，那就是当您想要测试推送通知时。
如果您在开发配置文件上测试推送通知，则需要使用开发推送通知证书将您的推送通知发送到 Apple 沙箱 APNS 服务器的 SSL 连接。
如果您想使用生产推送通知证书和实时 APNS 服务器测试推送通知，则必须使用分发证书和临时配置文件将应用程序部署到设备（其中包括执行 Entitlement.plist 步骤，其中如果您仅使用开发人员配置文件，通常可以跳过）。
另请注意，当您使用临时配置文件进行部署时，您的设备令牌将与使用开发配置文件时使用的设备令牌不同。这是测试 APN 的推荐方法，因为在 Ad Hoc 构建和 AppStore 上的最终实时部署之间不需要进行后端更改。
There's one situation in which you need an Ad Hoc profile, and that's when you want to test Push Notifications.
If you test Push Notifications on a Development Provisioning Profile, your push notifications need to be sent using the Development Push Notification Certificate for your SSL connections to Apple's sandbox APNS server.
If you want to test Push Notifications using your Production Push Notification Certificate and the live APNS servers, you'll have to deploy your app to a device using a Distribution Certificate and Ad Hoc Provisioning Profile (which includes doing the Entitlement.plist steps, which you can ordinarily skip if you were only using Developer Provisioning Profiles).
Also note that when you deploy using an Ad Hoc profile, your device token will be different from the one you use when you're using the development profile. This the recommended way to test APN because there's no back end changes that need to be made between the Ad Hoc build and the final live deployment on the AppStore.
Ad-Hoc 不适合开发人员，而是适合测试人员。没有 iPhone SDK / XCode，只有 iTunes。
（答案是：没有开发者证书就可以安装ad-hoc应用程序，而使用开发应用程序则不能安装）
Ad-Hoc is not for developers, but for testers. Who do not have iPhone SDK / XCode, iTunes only.
(The answer is: you can install ad-hoc app without developer certificate, and can't do it with development app)
方法 1：从 XCode 安装
开发配置文件要求您（最初）从 XCode 中运行应用程序。
这具有将设备标记为用于开发的副作用，而且还要求您将 iPhone/iPod Touch 连接到运行 XCode 的机器。从 XCode 运行应用程序后，该应用程序就会安装在设备上，并且您不再需要连接到计算机即可运行它。 （直到您想要更新应用程序。）
方法 2：从 iTunes 安装
Ad-Hoc 配置文件允许您将应用程序提供给任何人，并让他们使用 iTunes 自行安装。您发送它们：
他们选择这两个并将它们拖到 iTunes 上。然后同步。
稍后，您可以仅向他们提供该应用程序的更新版本（无需临时配置配置文件，因为他们已经在其设备上安装了该配置文件），并且他们可以将新应用程序拖到 iTunes 图标上以安装新版本。
Ad-Hoc 分发的一个限制是，它要求您将每个设备 ID 输入 iPhone 开发门户。每年的设备 ID 数量上限为 100 个（您不能删除任何 ID，直到下一年开始 - 只能添加它们）。对于大多数开发人员来说，100 个 ID 的限制不会成为障碍，只需记住，您需要提前获取设备 ID，然后再创建 Ad-Hoc 配置文件以发送给您想要安装应用程序的人员。
Method 1: Install from XCode
The Development Provisioning Profile requires you to run the app (initially) from within XCode.
This has the side-effect of marking the device as being used for development, but also requires you to connect the iPhone/iPod Touch to the machine running XCode. Once you run the app from XCode, the app is installed on the device and you no longer need to be connected to the machine to run it. (Until you want to update the app.)
Method 2: Install from iTunes
An Ad-Hoc provisioning profile allows you to give the app to anyone and let them install it themselves using iTunes. You send them:
They select these two and drag them onto iTunes. Then sync.
Later, you can give them an updated version of the app only (without the Ad-Hoc Provisioning Profile, since they've already installed that on their device) and they can drag the new app onto the iTunes icon to install the new version.
One limitation to Ad-Hoc distribution, is that it requires you to enter each Device ID into the iPhone Development Portal. And there is a limit to 100 device IDs per year (you cannot erase any IDs, until your next year begins -- only add them). The 100-ID limit will not be a hindrance for most developers, just keep in mind that you need to get the device ID ahead of time, before you create the Ad-Hoc Provisioning Profile to send to the person you want to install your app.