没有可用于登录 Xcode 5 的身份

No Identities are available for signing in Xcode 5

提问by Kurt Watts

I have followed every direction given here but in-vain.

我遵循了这里给出的每一个方向，但都是徒劳的。

Created/Added distribution provisioning profile (1000 times) Deleted and created certificates. Added them to keychain. Create distribution profile using new certificate.

创建/添加分发配置文件（1000 次） 删除和创建证书。将它们添加到钥匙串。使用新证书创建分发配置文件。

I get no warning or error when i build the app. It is only when i am trying to archive the app to create ad-hoc distribution i get No Identities are available for signing warning. If I try use download Identities, Xcode crashes.

我在构建应用程序时没有收到警告或错误。只有当我尝试存档应用程序以创建临时分发时，我才会收到无身份可用于签名警告。如果我尝试使用下载身份，Xcode 会崩溃。

This started to happen ever since I upgraded to Xcode 5.

自从我升级到 Xcode 5 后，这种情况就开始发生了。

Certificate as well as profile have Valid status. Also I made sure to pick correct distribution provisioning profile under code signing identity for both target and project.

证书以及配置文件具有有效状态。此外，我确保在目标和项目的代码签名标识下选择正确的分发配置文件。

Here is one of the links i followed.

这是我遵循的链接之一。

https://stackoverflow.com/questions/13592074/no-identities-are-available-for-signing

https://stackoverflow.com/questions/13592074/no-identities-are-available-for-signing

回答by johndpope

Xcode 5

Xcode 5

1) Recreate the distribution profile in developer.apple.com with a different name.

1) 在 developer.apple.com 中使用不同的名称重新创建分发配置文件。

download / open

下载/打开

cmd + , - > preferences > accounts > view details > sync /refresh

cmd + , - > 首选项 > 账户 > 查看详情 > 同步/刷新

3) under the Build Settings

3）在构建设置下

Provisioning profile > Release > Select the new Provisioning profile.

供应配置文件 > 发布 > 选择新的供应配置文件。

Above - in code signing identity and it should magically appear.

上面 - 在代码签名标识中，它应该神奇地出现。

回答by mservidio

Ran into this issue today also when trying to create Ad Hoc builds for upload to TestFlightApp. Fixed it by updating the Target - Code Signing Provisioning Profile section. Set the Release Provisioning Profile to point to your Ad Hoc profile. Then when you create a package from the Archive menu item it will use the correct profile for Ad Hoc distribution. This looks to be new in XCode 5.

今天在尝试创建 Ad Hoc 构建以上传到 TestFlightApp 时也遇到了这个问题。通过更新目标 - 代码签名配置文件部分修复了它。将 Release Provisioning Profile 设置为指向您的 Ad Hoc 配置文件。然后，当您从存档菜单项创建包时，它将使用正确的配置文件进行临时分发。这在 XCode 5 中看起来是新的。

回答by MScottWaller

I ran into the same problem. I spent about 3 weeks on it. I remade my app from scratch. I must have remade certificates and provisioning profiles dozens of times. Everything was case sensitive and matched perfectly. Everything was set in both the project and target sections.

我遇到了同样的问题。我花了大约 3 周的时间。我从头开始重新制作我的应用程序。我必须重新制作证书和配置文件数十次。一切都区分大小写并完美匹配。一切都在项目和目标部分中设置。

In the end, I decided to skip ad hoc validation and chose a regular distribution profile validation. Then the app finally validated perfectly, no issues.

最后，我决定跳过临时验证并选择常规分发配置文件验证。然后应用程序终于完美验证，没有问题。

And when I clicked distribute instead of validate, XCode let me choose the ad hoc profile, and thus far I've been able to beta test smoothly.

当我点击分发而不是验证时，XCode 让我选择临时配置文件，到目前为止我已经能够顺利进行 beta 测试。

In short, I haven't been able to validate with an ad hoc profile, but I've found the way around it. Haven't submitted to the App Store yet, but the fact that I was able to validate with a regular distribution profile gives me hope.

简而言之，我无法使用临时配置文件进行验证，但我已经找到了解决方法。尚未提交到 App Store，但我能够使用常规分发配置文件进行验证这一事实给了我希望。

Hope this helped.

希望这有帮助。

回答by Peter

Instead of using Xcode to submit the app I have used the Application Loader app based on this tutorial.

我没有使用 Xcode 提交应用程序，而是使用了基于本教程的 Application Loader 应用程序。

I ran into validation issues though - oh joy :-P

不过我遇到了验证问题 - 哦，喜悦 :-P

回答by Keely

I had a similar problem. I think the solution is to set the provisioning profile and identity in both the project and target sections of the project navigator. After I did the on in the project, the identities were found. Hope this helps!

我有一个类似的问题。我认为解决方案是在项目导航器的项目和目标部分中设置配置文件和身份。我在项目中做完之后，找到了身份。希望这可以帮助！

回答by thatzprem

Goto Xcode>> Preferencesand associate with an apple developer program with the appleID linked with your current provisioning profile.

转到Xcode>>Preferences并关联一个苹果开发者程序，其 appleID 与您当前的配置文件相关联。

回答by Ray Fix

For what it is worth I had a very similar issue. It didn't start happening to me after Xcode 5 but after I accidentally reset my keychain. (I was trying to reset the keychain of a remote machine, and accidentally did it to my own. Doh!)

对于它的价值，我有一个非常相似的问题。它没有在 Xcode 5 之后发生在我身上，而是在我不小心重置了我的钥匙串之后。（我试图重置远程机器的钥匙串，但不小心将其重置为我自己的。Doh！）

Once you get to that screen in Xcode you are done. Any option you select from there results in an Xcode crash. 100% repeatable. I reported that and hopefully it will get fixed in a future update.

在 Xcode 中到达该屏幕后，您就完成了。您从那里选择的任何选项都会导致 Xcode 崩溃。100% 可重复。我报告了这一点，希望它会在未来的更新中得到修复。

The solution that I stumbled into was that I didn't have to correct provisioning profile on my machine. I had to download it double click and get it into the keychain. I don't actually see it in the keychain but it shows up in Xcode where I suddenly get a new option in code signing identities that didn't exist before. I set this to Automatic.

我偶然发现的解决方案是我不必在我的机器上更正配置文件。我必须双击下载它并将其放入钥匙串中。我实际上并没有在钥匙串中看到它，但它出现在 Xcode 中，我突然在代码签名身份中获得了一个以前不存在的新选项。我将其设置为自动。

If you had told me that this was the solution to this problem I would have laughed at you because I would have said I ALREADY DID THAT 5 TIMES! Maybe in the process of resetting, revoking, and reinstalling I forgot it? Although I can see all of the certificates in keychain, I don't actually know how to see the provisioning profiles. For me, when I put in the new provisioning profile it shows up in Xcode as code signing identity option that wasn't there before.

如果你告诉我这是这个问题的解决方案，我会嘲笑你，因为我会说我已经这样做了 5 次！也许在重置、撤销和重新安装的过程中我忘记了？虽然我可以看到钥匙串中的所有证书，但我实际上不知道如何查看配置文件。对我来说，当我放入新的配置文件时，它在 Xcode 中显示为以前不存在的代码签名标识选项。