Xcode 8显示配置配置文件不包含签名证书的错误。
此问题仅适用于Xcode-8和Xcode 7,相同的配置文件显示相关已识别的证书。
Xcode 8显示配置配置文件不包含签名证书的错误。
此问题仅适用于Xcode-8和Xcode 7,相同的配置文件显示相关已识别的证书。
当前回答
我也有同样的问题。 我换了mac。当我下载Xcode证书时,我收到了一条错误消息:“错误是安全配置文件不包括证书签名。”
1)登录https://developer.apple.com/account/ios/profile/limited/edit Select the project => edit => Certificates => Select All => Create => Download
2)在Xcode中:项目文件=>签名(调试)=>配置文件=>导入文件=>选择带1的文件
其他回答
对于那些仍然在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.
检查你的钥匙链,也许你有一个重复的证书。
为了解决这个问题,
我只是在项目设置通用选项卡上启用了“自动管理签名”,在启用之前,我担心它可能会有一些副作用,但一旦我启用,它就为我工作了。
此问题是由于您的配置文件中的证书中的私钥与您的密钥链中的私钥不匹配。我解决这个问题的方法是
delete all iPhone Developer certificate in keychain. delete all certificate in apple account. using xcode "Manage Certificates" to add certificate, sometime you still have certificate in your Mac, but I do not know where it is for now, and if added successfully, your apple account will display that certificate too, and then you can create your profile with that certificate and download ... goto 5 if you use "Manage Certificates" can't add certificate, you can create a new certificate, and do remain steps. finish.
Xcode版本8的代码签名问题也是如此。
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.
我为此挣扎了很多天。
步骤1: 删除所有证书,配置文件,appID,密钥等从开发帐户。
步骤2: 重新创建推送通知证书、配置文件、应用ID等。
步骤3: 从keychain中删除所有证书。
步骤4: 清除~/Library/MobileDevice/ provisioning Profiles中的所有配置文件。
步骤5: 只添加了所需的配置文件并进行了测试。它工作得很好。