一个 Xcode 管理器中有多个证书/配置文件？
这里有几个类似的问题，但没有一个可以回答我的基本问题：
是否可以在钥匙串中拥有两个单独的开发人员证书，并在管理器中拥有两个相应的分发配置文件？
我有自己的（工作）开发人员证书和我自己的 iPhone 应用程序的配置文件。 现在，我为客户完成了一个项目，并想使用他的开发者帐户/证书/配置文件将他的应用程序提交到他帐户上的应用程序商店。
这可能吗？
到目前为止，我下载并安装了他的证书，它们显示在我的钥匙串中，并且我在管理器中安装了他的配置文件，但管理器告诉我“在您的钥匙串中找不到与此配置文件匹配的有效签名身份。”。 同样，存档构建也会失败。
我找不到一种方法来告诉组织者使用我客户的证书而不是我自己的证书 - 我认为这就是问题所在。
感谢您的帮助！
There are several similar questions here, but none could answer my basic question:
Is it possible to have two separate developer certificates in the keychain and two corresponding distribution profiles in Organizer?
I have my own (working) developer certificate and provisioning profile for my own iPhone apps.
Now I finished a project for a client and would like to use his developer account/certificates/provisioning profiles to submit his app to the app store on his account.
Is that even possible?
So far I downloaded and installed his certificates and they show up in my keychain, and I installed his provisioning profile in Organizer, but Organizer tells me "A valid signing identity matching this profile could not be found in your keychain.".
Likewise, the archive build fails.
I couldn't find a way to tell Organizer to use the certificate of my client instead of my own-I think this is the problem.
Thanks for any help!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
是的，我已经使用客户的分发证书多次为客户生成了应用程序商店版本的项目。无需使用他们的开发者证书。这里有很多事情可能会出错，如果您有权访问客户的帐户，您可以进入配置门户并检查一下：
确保项目设置中的捆绑包 ID 与应用程序上的应用程序 ID 完全匹配iOS 配置门户（通常为 com.company.appname）
确保应用商店分发配置文件被标记为“有效”并显示在分发证书下。
确保 xcode 中的应用商店构建配置引用客户端的分发证书。
打开您的钥匙串并确保客户端分发证书也有其随附的私钥。这可能就是问题所在，这是通常被遗漏的部分。客户端必须导出其 dist 证书的私钥，并将其以 .p12 文件的形式连同 .p12 文件的密码一起发送给您。如果没有私钥，则无法使用 dist 证书对应用程序进行签名！
有时只需退出 Xcode 并重新启动它就会有所帮助。
Yes I've produced app store builds of projects for clients several times using their distribution certificate. No need to use their developer certificate. There are many things can could go wrong here, if you have access to the client's account you can go on to the provisioning portal and check things out:
make sure the bundle ID in the project settings exactly matches the app ID on the iOS provisioning portal (com.company.appname usually)
make sure the app store distribution provisioning profile is marked as "valid" and shows up under the distribution certificate.
make sure the app store build config in xcode references the client's distribution cert.
open your keychain and make sure that the client distribution cert also has its accompanying private key. This may be the problem, it's the part usually left out. The client must export his private key for his dist cert and send it to you in the .p12 file along with the password to the .p12 file. The dist cert can't be used to sign the app without the private key!
sometimes just quitting Xcode and restarting it helps.
请参阅此解决方案以重复证书： http:// /tapadoo.com/2012/certificates-magically-re-appearing-in-your-keychain-try-this/
要点是，如果您有旧的私钥和配置文件，您可能会遇到Xcode 将在您的钥匙串中重新创建旧证书的情况。这将使代码签名成为笑点，因为它需要具有给定名称的单个证书。删除旧的私钥将解决此问题。
See this solution to duplicate certificates: http://tapadoo.com/2012/certificates-magically-re-appearing-in-your-keychain-try-this/
The gist is that if you have an old private key and provisioning profile around, you can run into a case where Xcode will re-create an old certificate in your keychain. This will make code signing gag because it requires a single certificate with a given name. Deleting the old private key will resolve this issue.
简单模式
（我非常讨厌这些过时的导出错误。浪费了很多时间。我不信教，但我仍然祈祷这对您有帮助）
注意：如果您尝试导出存档，可以将导出窗口保持打开状态，删除配置文件，然后单击“重试” “或者按钮所说的任何内容。这将使您不必一遍又一遍地重新存档
#xcode8.2.1 #osx10.11.6
EASY MODE
(I hate these archaic export errors so bad. So many hours wasted. I'm not religious but I still pray this helps you)
Note: if you're trying to export an archive, you can leave the export window open, delete a provisioning profile, then click "retry" or whatever the button says. This will save you from have to re-archive over and over
#xcode8.2.1 #osx10.11.6