Delete the developer certificate that does not have a private key. Delete the provisioning profile from your machine using go to folder (~/Library/MobileDevice/Provisioning Profiles) Then first check then uncheck the Automatically manage signing option in the project settings with selecting team. Sing in Apple developer account and edit the provisioning profile selecting all available developer certificates then download and add to XCODE. Select the provisioning profile and code signing identity in project build settings

Delete the developer certificate that does not have a private key. Delete the provisioning profile from your machine using go to folder (~/Library/MobileDevice/Provisioning Profiles) Then first check then uncheck the Automatically manage signing option in the project settings with selecting team. Sing in Apple developer account and edit the provisioning profile selecting all available developer certificates then download and add to XCODE. Select the provisioning profile and code signing identity in project build settings

我取消勾选，然后勾选“自动管理签名”选项。这为我解决了问题。

此问题是由于您的配置文件中的证书中的私钥与您的密钥链中的私钥不匹配。我解决这个问题的方法是

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.