XCode不接受“ iOS发行版”代码签名实体设置 [英] XCode doesn't honor the "iOS Distribution" Code Signing Entity setting

问题描述

我想正确地理解Code Signing Identity设置：我想在Xcode中使用自动设置，而不指定特定的身份。自动设置有2个选择：iOS Developer和iOS Distribution。基于您使用的那个，应该切换到从您的钥匙串中选择开发者或发行签名的身份。

I want correctly understand the Code Signing Identity setting: I want to use the automatic setting in Xcode and not specify a specific identity. The automatic setting has 2 choices: iOS Developer and iOS Distribution. Based on which one you use, it's supposed to switch to choose a developer or a distribution signing identity from your keychain.

我的构建设置按如下配置在构建中使用 iOS发行版标识：

I have my build settings configured as follow, in order to use an "iOS Distribution" identity on build:

当我存档我的应用程序时（存档方案已正确设置为使用 Release 构建配置），我发现Xcode没有使用正确的代码签名身份：

When I Archive my app (the Archive scheme is correctly set to use the Release build configuration), I see that Xcode is not using the correct code signing identity:

任何人都知道为什么会这样吗？我正在寻找一种解释，而不是一种解决方法（我知道我可以通过直接从钥匙串将代码签名身份设置为我的 iPhone发行版：公司名称身份来解决此问题）

Anyone would know why this is the case? I'm looking for an explanation and not a workaround solution (I know I can work around the problem by directly setting the Code Signing Identity to my iPhone Distribution: Company Name identity from the keychain)

谢谢！

推荐答案

所以有趣的是，这实际上与最新的无关紧要只要您最终将要使用的配置文件的Xcode与现在使用其签名的包标识符相同，就使用......

So interestingly this doesn't actually matter in the latest Xcode as long as the profile you are eventually going to sign with is for the same bundle identifier as the one its signing with now...

只要团队设置设置为Xcode能够自动生成所需的配置文件。

As long as the team setting is set Xcode is capable of generating the profile you need automatically. Don't try to fight it.

这是目标的常规设置屏幕中的团队设置：

Here is the Team setting from the Target's General settings screen:

然后在归档Xcode时将归档文件放入组织器中。当您在管理器窗口中单击存档上的分发时，它会提示您选择一个新的签名身份并实际上重新签名了该应用程序。

Then when you archive Xcode puts the archive in the organiser. When you click distribute on the archive in the organiser window it prompts you to select a new signing identity and actually re-signs the app.

它实际上可以用Xcode生成的团队配置文件。您也无需创建特定的临时配置文件，因为您的测试人员现在可以安装使用开发配置文件签名的应用程序，而不会出现任何问题。唯一需要制作自己的配置文件的时间是，如果您使用任何具体的捆绑包ID功能，例如推送通知，游戏中心，数据保护，iCloud，应用间音频，存折，钥匙串访问组或应用内

It actually works to sign apps with the team provisioning profiles generated by Xcode. You also don't need to make an ad-hoc specific provisioning profile as your testers can now install apps signed using the development provisioning profiles with no issues. The only time you will need to make your own provisioning profile is if you are using any of the concrete bundle id features like push notifications, game centre, data protection, iCloud, inter-app audio, passbook, keychain access groups or in-app purchase.

如果您为特定的捆绑包ID设置了自己的配置文件，则Xcode会在选择时自动选择相关的配置文件，或可供选择

If you make your own provisioning profiles for specific bundle ids then Xcode will either automatically select, or have available for selection, the relevant provisioning profile at the point of choosing the identity in the organiser window.

您可以从Xcode设置的帐户窗格中刷新Xcode的配置文件缓存。单击您的团队，单击查看详细信息，然后单击左下角的刷新按钮

You can refresh Xcode's cache of provisioning profiles from the Accounts pane of Xcode's settings. Click on your team, Click "View Details" and then click the tiny refresh button in the bottom left corner

这篇关于XCode不接受“ iOS发行版”代码签名实体设置的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！