Xcode 6.3 - 您已经拥有当前的 iOS 开发证书或待处理的证书请求

Xcode 6.3 - You already have a current iOS Development certificate or a pending certificate request

提问by dave

Xcode as of 6.3 is no longer allowing me to automatically perform device provisioning for a client. Has anyone else experienced this issue? I found no results when searching for this on Google...

从 6.3 开始，Xcode 不再允许我为客户端自动执行设备配置。有没有其他人遇到过这个问题？我在谷歌上搜索这个时没有找到结果......

This client has their own bundle ID and it's possible they also have their own provisioning profile for this device. So maybe Apple is matching up the bundle ID irrespective of the developer account being used for provisioning.

此客户端有自己的捆绑 ID，并且他们可能也有自己的此设备的配置文件。因此，无论用于配置的开发人员帐户如何，Apple 都可能会匹配捆绑 ID。

I was able to address the issue by modifying the app's bundle ID and manually going through the provisioning process, but I'm guessing this issue is extremely rare, so I'm not sure if this post will be of use to anyone.

我能够通过修改应用程序的包 ID 并手动完成配置过程来解决这个问题，但我猜这个问题非常罕见，所以我不确定这篇文章是否对任何人有用。

回答by David

I just found that if I remove my account from Xcode, and then sign in again, it solved the issue. I did revoke my existing certificates and request new ones though as part of that process. I didn't import an existing profile.

我刚刚发现，如果我从 Xcode 中删除我的帐户，然后再次登录，它就解决了这个问题。作为该过程的一部分，我确实撤销了我现有的证书并申请了新证书。我没有导入现有的配置文件。

回答by Vivek

When I am create new certificate from my Xcode 9.2 the error was appear "You already have a current iOS Distribution certificate or a pending certificate request".

当我从我的 Xcode 9.2 创建新证书时出现错误 "You already have a current iOS Distribution certificate or a pending certificate request"。

Just 2 step for fix this error.

只需 2 步即可修复此错误。

1. Remove old certificate from developer.apple.com
2. Create new certificate from Xcode or developer.apple.com

1. 从 developer.apple.com 删除旧证书
2. 从 Xcode 或 developer.apple.com 创建新证书

My problem has been solved (I am using Xcode 9.2).

我的问题已解决（我使用的是 Xcode 9.2）。

回答by Moshe

This issue is actually more common than you think.

这个问题实际上比你想象的更常见。

Some Solutions:

一些解决方案：

I usually find that opening Xcode's settings and signing out of my account and the signing in again resolves most of those issues.

我通常发现打开 Xcode 的设置并退出我的帐户并再次登录可以解决大部分问题。

You may have an older mac that already used up that one allotted development certificate. In that case you'll want to export the developer profile from that machine. If you no longer have access to that machine, it may be time to invalidate that certificate and simply request a new one.

您可能有一台较旧的 mac，它已经用完了分配的开发证书。在这种情况下，您需要从该机器导出开发人员配置文件。如果您不再有权访问该机器，则可能是时候使该证书无效并简单地请求一个新证书。

Another option may be to double check your build settings in your project and ensure that it's looking for the right certificate. It's fairly common in my experience for these settings to make decisions on their own, and confirming that they're what you expect may help.

另一种选择可能是仔细检查您项目中的构建设置，并确保它正在寻找正确的证书。根据我的经验，这些设置自行做出决定并确认它们是您所期望的可能会有所帮助，这是相当普遍的。

Background:

背景：

When dealing with provisioning, it's really easy to get caught up with the frustration of all of the steps you need to go through. The first thing to note is if the error you see is talking about a "Certificate" or a "Profile." In your case, it's a certificate. Good.

在处理配置时，很容易陷入对需要执行的所有步骤的挫败感中。首先要注意的是，您看到的错误是关于“证书”还是“配置文件”。在你的情况下，它是一个证书。好的。

Certificates differ from provisioning profiles in a few ways. Certificates are usually only generated twice: once for development, and once for distribution. (Exceptions to this rule are if you decide to add support for some of the special features like push notification or for generating passbook passes on a server.)

证书在几个方面不同于配置文件。证书通常只生成两次：一次用于开发，一次用于分发。（此规则的例外情况是，如果您决定添加对某些特殊功能的支持，例如推送通知或在服务器上生成存折。）

The process for generating certificates is also a little more bureaucratic than profiles. You requesta certificate from Apple's Member Center. You generatea provisioning profile.

生成证书的过程也比配置文件更官僚。您从 Apple 的会员中心申请证书。您生成一个配置文件。

The reason for the word requestvs generateis because both Apple and your iOS team's admin need to approve certificate requests. This is because certificates identify you as part of your iOS developer team, and offer all the powers associated with that.

使用“请求”与“生成”一词的原因是，Apple 和您的 iOS 团队的管理员都需要批准证书请求。这是因为证书将您标识为 iOS 开发团队的一员，并提供与此相关的所有权力。

For the sake of completeness, I'll add that provisioning profiles are generated based on that certificate, and really only tell iOS what environment your app is meant to run in. (On any device via the store, specific devices, etc.)

为了完整起见，我将补充说，配置文件是基于该证书生成的，并且实际上只告诉 iOS 您的应用程序打算在什么环境中运行。（通过商店、特定设备等在任何设备上）

Now, the important part for you is the request business. Most people don't pay much attention to this terminology, since indie developers and small teams (where the developers are admins) don't require developers to ask for permission.

现在，对您来说重要的部分是请求业务。大多数人不太注意这个术语，因为独立开发人员和小团队（开发人员是管理员）不需要开发人员请求许可。

Your error is talking about a previously generated certificate or request. You can only have one development certificate per developer. You either have one, or you've requested one and someone has to approve.

您的错误是关于先前生成的证书或请求。每个开发人员只能拥有一个开发证书。你要么有一个，要么你已经请求了一个并且必须有人批准。

That's what's happening here.

这就是这里发生的事情。

回答by Vaiden

My team has maxed out on release certificates, because apparently there is a quota. We had to delete one of the existing release certificates.

我的团队已经用尽了发布证书，因为显然有配额。我们不得不删除现有的发行证书之一。

回答by Logesh R

This process is made simple with Xcode 8.3 and 9. Just delete one of your old certifcates in the "validate" interface and click the plus button to request new one, Xcode will request for you and add it in keychain. in my case, maximum number was reached, so I deleted one which was lost in a old Mac and created new one.

这个过程在 Xcode 8.3 和 9 中变得简单。只需在“验证”界面中删除您的旧证书之一，然后单击加号按钮请求新证书，Xcode 会请求您并将其添加到钥匙串中。就我而言，已达到最大数量，因此我删除了旧 Mac 中丢失的一个并创建了一个新的。

回答by Amit Pandey

Delete old developer certificate from https://developer.apple.com/account/ios/certificate/and try to create developer certificate from xcode

从https://developer.apple.com/account/ios/certificate/删除旧的开发者证书并尝试从 xcode 创建开发者证书