Xcode 4：构建存档配置文件是否特定？
我还没有真正使用过 Xcode 3 下的存档功能，但现在在 Xcode 4 中已经习惯了。到目前为止，我在所有项目中总是使用三到四个构建设置：调试、分发 AdHoc 和分发 AppStore。地区。 AdHoc 和 AppStore 都是“Release”的副本，仅在为 Codesigning 选择的配置文件方面有所不同（因此本质上它们是为了方便起见，确保我不会向错误的人发送错误签名的版本）。
现在我注意到，每当我从组织者导出存档的构建时，Xcode 都会询问我想要使用哪个配置文件来签署我的构建，但同时，如果构建设置中所选的配置文件无效，构建也会失败。 Xcode 4 存档配置文件是独立于配置文件还是与配置文件相关？如何解决在没有太多构建设置组的情况下必须为 AdHoc 和 AppStore 进行构建的“挑战”（在 Xcode 4 中切换与构建方案关联的组已变得有些麻烦）？
谢谢！
I haven't really used the archive function under Xcode 3, but got used to it now in Xcode 4. So far I always used to have three or four build settings in all my projects: Debug, Distribution AdHoc and Distribution AppStore. Distr. AdHoc and AppStore were both copies of "Release" and only differed in regard to their provisioning profile selected for Codesigning (so essentially they were a thing of convenience, making sure I never sent the wrong person the wrongly signed build).
Now I noticed that Xcode asks me with which profile I would like to sign my build with whenever I export an archived build form the organizer, yet at the same time the build would also fail if the selected provisioning profile in the build settings was not valid. Are Xcode 4 archives provisioning profile independent from or are thy tied to a provisioning profile? How do you solve the "challenge" of having to build for AdHoc and AppStore without having too many build settings groups (switching the groups associated with the build schemes has become somewhat cumbersome in Xcode 4)?
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
在 Xcode 4 中，如果您归档应用程序，它将使用您指定在其构建配置下使用的配置文件进行签名。很可能是从 Xcode 3 项目继承的设置。
存档的应用程序可以在稍后使用不同的配置文件进行退出（通过组织者或命令行），因此在某种程度上，是的，它们独立于配置文件。
关于管理 AdHoc 和 AppStore 构建的两个建议：
1)
第一个是利用 Xcode 4 方案，并
在方案菜单下为 AdHoc 和 AppStore 创建新方案：编辑方案 -> 。复制方案，然后在存档下您可以选择所需的构建配置（AdHoc、AppStore 等），然后您可以将此方案命名为 AdHoc、AppStore 来匹配。当您想要构建以供发布时，只需选择目标方案，它将使用构建配置中的关联配置文件对其进行签名。
2）
维护 1 方案，从构建配置中删除代码签名，并在存档后通过组织器专门对应用程序进行代码签名。
in Xcode 4 if you archive an application it is signed with the provision profile that you have indicated to use under its build configuration. Most likely a settings that was carried over from an Xcode 3 project.
An archived app can be resigned with a different provision profile at a later time (though the organizer or command line), so in a way, yes they are independent of provision profile.
Two suggestions for managing building for AdHoc and AppStore:
1)
The first is taking advantage of Xcode 4 schemes, and creating a new schemes for AdHoc and AppStore
Under the Schemes Menu: Edit Scheme -> Duplicate Scheme, then under the Archive you can select your desired build configuration (AdHoc, AppStore, etc...), you can then name this scheme AdHoc, AppStore to match too. When you want to build for release just select the target scheme and it will sign it with the associated provision profile from the build configuration.
2)
Maintain 1 scheme, remove code signing from your build configurations, and code sign apps exclusively though the organizer after archiving.