Xcode 8显示配置配置文件不包含签名证书的错误。

此问题仅适用于Xcode-8和Xcode 7,相同的配置文件显示相关已识别的证书。


当前回答

对于那些仍然在Xcode8中与这个问题作斗争的人。对于我来说,这是一个重复的证书问题,这是我解决它的方法:

我读了尼克的回答,然后开始了我的调查。我检查了我的特定案例中的所有密钥和证书(在~/Library/Keychains/System.keychain中)。

When I opened the file, I found that I had two iPhone Distribution Certificates (that was the certificate that Xcode was requesting me), one with the iOS Distribution private key that I have been using since the beginning, and another iPhone Distribution Certificate which its private Key had a name (iOS Distribution:NAME) that wasn´t familiar for me. I deleted this last certificate, started Xcode again and the problem was gone. xCode wasn´t able to resolve that conflict and that´s why it was giving signing certificate error all the time.

检查你的钥匙链,也许你有一个重复的证书。

其他回答

您还可以使用Fastlane工具包解决代码签名问题。作者投入了大量精力来有效地自动化构建、签名iOS应用程序(等等)。

因此,在上述套件中,有一个工具sigh,它神奇地解决了任何签名问题,因此得名:)这里的好处是,这个工具封装了关于常见签名问题的知识,可以检测和解决大多数问题。

Fastlane安装为Ruby gem:

Gem安装fastlane

然后简单地引用:

快速的叹息——发展

回答两个问题,瞧:

[11:56:55]: No existing profiles found, that match the certificates you have installed locally! Creating a new provisioning profile for you
[11:57:01]: Creating new provisioning profile for 'com.myapp' with name 'com.myapp Development'
[11:57:06]: Downloading provisioning profile...
[11:57:09]: Successfully downloaded provisioning profile...
[11:57:09]: Installing provisioning profile...

最后,进入Build Settings -> Signing,切换到新创建的配置文件,其名称您刚刚在命令回显中看到。

此示例用于开发代码签名问题(在设备上运行)。查看所有其他选项的叹息文档。

对于那些应该继续使用不自动的原因

打开keyChain访问,看看是否有两个相同的认证,如果有两个或更多,只需删除到一个,它将工作:)

我也有同样的问题。 我换了mac。当我下载Xcode证书时,我收到了一条错误消息:“错误是安全配置文件不包括证书签名。”

1)登录https://developer.apple.com/account/ios/profile/limited/edit Select the project => edit => Certificates => Select All => Create => Download

2)在Xcode中:项目文件=>签名(调试)=>配置文件=>导入文件=>选择带1的文件

I haven't seen this mentioned yet but if you are still having issues after recreating your provisioning profiles, deleting the existing ones you have in your Provision Profiles folder, checking for dupes in your Keychain, etc (all other answers ITT), open your Target > Build Settings > Code Signing and make sure everything looks consistent in there. For example, I had changed the Code Signing Identify for Debug to a Distribution identity, which obviously wouldn't work as the Development Provisioning Profile doesn't have the Distribution certificate and was causing the error in the first place.

如果您尝试将应用程序上传到iTunes Connect(您的供应配置文件设置为分发),请转到项目设置->构建设置->代码签名。请确保将所有调试和发布选项设置为您的分发配置文件。