两个同名的 AppStore 帐户。我收到 codeSign 错误“名称”在钥匙串中出现多次
我在 AppStore 上获得了另一个新帐户，我在我的 MAC 上设置了新帐户证书。现在，当我尝试发布 XCode 时，出现错误
CodeSign 错误：证书标识 'iPhone 分发：'名称' 在钥匙串中出现多次。协同设计工具只需要一个。
如何更改其他帐户的证书身份？虽然我必须保留两个 iTunes 个人资料上的名字。 如何避免此问题，而无需每次需要在应用商店上发布应用程序时删除一个证书。
谢谢。
I got another new account for the AppStore, I setup the new account certificates on my MAC. Now when I try to publish XCode gives me the error
CodeSign error: Certificate identity 'iPhone Distribution: 'Name' appears more than once in the keychain. The codesign tool requires there only be one.
How can I change my certificate identity for the other account? While I have to leave my Name as it is on both itunes profiles.
How can avoid this problem without have to remove one certificate each time I need to publish app on appstore.
Thank you.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
查看 Mac 上的钥匙串应用。您可能有过期的条目以及当前的条目。删除过期的条目就可以了。今天为我工作。
Look in the keychain app on your Mac. You may have expired entries as well as current entries. Delete the expired entries and you will be okay. Worked for me today.
我为每个团队创建一个钥匙串，并将该团队的所有相关文件（公钥、私钥、证书）放在钥匙串中。唯一的缺点是，在为设备构建时，您必须将默认钥匙串设置为团队钥匙串。
I create a keychain for each team, and put all the related files (public key, private key, certificate) for the team in the keychain. The only downside is that you have to set your default keychain to the team keychain when building for a device.
我刚刚遇到了这个问题，我当前的临时解决方案是导出然后删除其中一个发行版标识，留下一个 XCode 满意的标识。因此，每次我想切换到不同的项目来进行分发时，我都必须导出、删除和导入，这并不理想。
我仍在寻找更好的解决方案。
钥匙串方法原则上听起来不错，但实际上似乎需要使用“钥匙串首选项”中的“重置默认钥匙串”选项，我还没有尝试过，但听起来不像是低风险活动。
I have just had this problem, and my current temporary solution was to export then delete one of the distribution identities, leaving me with one identity which then XCode is happy with. So I will have to export, delete, and import each time I want to switch to a different project to make a distribution, which isn't ideal.
I am still looking for a nicer solution.
The keychain approach sounds ok in principle, but in practice it appears to be require using the "Reset the default keychain" option in Keychain Preferences, which I have not tried yet but doesn't sound like a low-risk activity.
我确实使用多个证书（对于相同的身份，又名“我”）在多个应用程序商店帐户上发布了多个应用程序，并且 Xcode 设法了解到目前为止哪个应用程序使用哪个证书（我可能必须通过选择正确的证书来帮助他）不时在“项目信息”菜单中手动配置配置文件）。
我正在做的是为我正在处理的每个新的“应用程序商店”帐户创建一个新证书，当然永远不要与应用程序 ID 发生冲突。这意味着我的钥匙串充满了“iPhone 开发人员 - Ben (XDFUHSD)”、“iPhone 开发人员 - Ben (DSUKJNSD)”等...证书，每个证书用于不同的客户端。
Xcode 确实会给我您不时提到的错误，但它实际上只在我的一个证书已过期并且我刚刚重新下载了一个新证书时才会发生。
希望这有帮助
I did publish multiple apps on multiple app store accounts using multiple certificate (for the same identity, aka "me") and Xcode manages to understand which certificate to use for which app so far (i may have to help him out by selecting the correct provisionning profile manually from time to time in the "project info" menu).
What i'm doing is to create a new certificate for every new "app store" account i'm working on, and of course never collide the app ids. That means my keychain is full of "iPhone developer - Ben (XDFUHSD)", "iPhone developer - Ben (DSUKJNSD)", etc... certificates, each beeing used for a different client.
Xcode does give me the error you mention from time to time, but it really only happens when one of my certificate has expired and i've just redownloaded a new one.
Hope this helps
无论如何，即使我的钥匙串中只有一份有问题的证书副本，我还是收到了此错误。我的设置中唯一奇怪的事情是我将 10.6 分区中的钥匙串文件添加到钥匙串访问中，因此我有两个“登录”钥匙串。尽管另一个根本没有任何证书，但当我将其从钥匙串访问中删除时，“出现多次”错误就消失了。
从好的方面来说，自动配置现在似乎工作得很好，所以清除并重新加载我的所有配置文件并不是我想象的噩梦。
For what it's worth, I got this error even though there was only one copy of the offending certificate in my keychain. The only odd thing about my setup was I'd added the keychain file from my 10.6 partition into Keychain Access, so I had two "login" keychains. Even though the other one didn't any certificates in it at all, the "appears more than once" error went away when I removed it from Keychain Access.
On the plus side, Automatic Provisioning seems to work pretty well these days, so clearing and reloading all my profiles wasn't the nightmare I'd thought it would be..