我收到了苹果公司的一封邮件:

Dear John Doe, The following certificate has either been revoked by a member of your development team or has expired: Certificate: iOS Development Team Name: Honey Team, LLC This does not affect apps that you've submitted to the App Store or your ability to update your apps. If you're using provisioning profiles that contain this certificate, they must be recreated before they can be reused. For details, see the "App signing overview" section of Xcode Help. Best regards, Apple Developer Program Support

我创建了一个新证书，撤销了之前的证书(在本地和任何其他开发人员的mac上)。为了让它工作，我必须下载新的配置文件。

解决方案是:

登录到苹果开发者帐户 删除/撤销以前以我的名字创建的证书。 将新的证书添加到供应配置文件中。您可以根据有效期来识别较新的 再次从Xcode下载。下载所有配置文件 重启Xcode

我个人没有这样的机会。这种访问权限只对我们团队的管理员开放，因此我没有截图，也不确定这些步骤是否100%正确。

我尝试了很多方法，但唯一解决这个问题的方法是在xcode中配置一些东西:

构建设置->签名:

代码签名标识:所有选项均选择iOS Developer。 代码签名风格:自动 配置文件:自动

我为此挣扎了很多天。

步骤1: 删除所有证书，配置文件，appID，密钥等从开发帐户。

步骤2: 重新创建推送通知证书、配置文件、应用ID等。

步骤3: 从keychain中删除所有证书。

步骤4: 清除~/Library/MobileDevice/ provisioning Profiles中的所有配置文件。

步骤5: 只添加了所需的配置文件并进行了测试。它工作得很好。

点击然后取消“启用自动签名”对我来说是有效的，尽管它所做的实际改变是:

Always_embed_swift_standard_libraries = yes;

或者在Xcode中，它被称为始终嵌入Swift标准库

您还可以使用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，切换到新创建的配置文件，其名称您刚刚在命令回显中看到。

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

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.