分发配置文件有效，但开发配置文件显示未找到有效的签名实体 [英] Distribution Provisioning Profiles are valid but Development Profiles say valid signing entity not found

问题描述

我在配置文件上花费了大量时间，甚至设法发布了一些应用程序，所以我熟悉这个过程.但是，我遇到了一个问题，我不知道该怎么做.

I've spent a ton of time with provisioning profiles, and even managed to release a few apps, so I'm familiar with the process. However, I've come across an issue and I'm not sure what to do.

在我的钥匙串访问中，我有大量的密钥和证书，其中很多都不熟悉.也许不明智，我将它们全部删除，以便重新添加正确的.(我现在意识到这是一个坏主意).

In my Keychain access, I had a ton of keys and certificates, a lot of which were unfamiliar. Perhaps unwisely, I deleted them all, in order to re-add the correct ones. (I now realise this was a bad idea).

在开发人员门户中，我意识到我的开发和分发证书即将到期，因此我撤销并重新创建了它们.(另外，我猜是个坏主意).在这样做时，我显然使我的所有配置文件无效.所以，我用新证书重新创建了它们.

In the developer portal, I realised my Development and Distribution certificates were about to expire, so I revoked and recreated them. (Also, I'm guessing a bad idea). In doing so, I obviously invalidated all my provisioning profiles. So, I recreated them all with the new certificates.

我现在遇到的问题是，当我将新的配置文件添加到 Xcode 时，分发证书(Ad Hoc 和 App Store)都显得有效.但是，我的开发配置文件(以及 iOS 团队配置文件 *)都显示未找到有效签名实体".

The problem I'm having now, is that when I add the new provisioning profiles to Xcode, the distribution certificates (Ad Hoc and App Store) both appear valid. However my development profiles (and the iOS Team profile *) all say 'Valid signing entity not found'.

通过删除我的本地证书、撤销在线证书、重新颁发它们并重新创建我的配置文件，我是否完全搞砸了事情?

By deleting my local certificates, revoking the online ones, reissuing them and recreating my provisioning profiles, have I totally messed things up?

推荐答案

我同意，即使经过几年，这仍然是一个非常复杂的领域.我认为，你不应该把事情搞得这么糟.如果您创建了一个新的签名请求和所有新证书，您应该没问题.但是，我记得可能会出现几个隐藏的问题.

I agree, this is still a very complicated area even after several years. I think, you should not be able to totally mess thing up like this. If you created a new signing request and all new certificates you should be fine. However, I remember several hidden issues that may appear.

首先是钥匙串中的重复证书.如果您的第一个证书已过期，并且您使用之前使用的相同签名请求生成另一个证书，则可能会发生这种情况.在这种情况下，Xcode 可能会以某种方式选择错误的.但是，如果您将它们全部清除并使用新的签名请求生成新证书，这应该不是问题.

First is the duplicated certificates in the keychain. This may happen if your first certificate has expired and you generate another one with the same signing request you used before. In this case Xcode somehow may pick the wrong one. However, if you cleaned them all and generated new certificates with the new signing request this should not be a problem.

其次，添加新证书后需要退出并重新启动Xcode.也许在新版本中，这不再是问题，但绝对是.此外，Xcode 将 Provisioning Profiles 缓存在 Organizer 中.如果您决定清理所有东西，也不要忘记清理它们.

Second, Xcode needs to be quit and relaunched after you added new certificates. Maybe in the new one it is not an issue any more, but it definitely was. Also, Xcode caches the Provisioning Profiles in the Organiser. If you decided to clean everything up do not forget to clean them too.

最后，确保目标设置中的代码签名身份确实使用新的配置文件.如果在 old once 和 new once 中使用相同的命名，很容易混淆它们.尝试更改新 Provisioning 配置文件的名称格式，以便您可以将它们与旧版本区分开来.我希望这会有所帮助.

And the last, make sure Code Signing Identity in the target settings really use the new profiles. If you use the same naming in the old once and new once it is easy to confuse them. Try to change names formats of the new Provisioning profiles, so you could distinguish them from the old once. I hope this helps.

这篇关于分发配置文件有效，但开发配置文件显示未找到有效的签名实体的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！