Having multiple iOS developer accounts and cannot create an IOS distribution certificate

Question

I have 2 valid single iOS developer accounts and 1 mac book air. To better explain my problem, I call my accounts account A and account B. My problem is that I can create developer and distribution certificates for account A. However, I cannot create a distribution certificate for account B with account name B. Account B of the distribution certificate accepts the name of account name A. To create certificates, I perform the following steps: Open access to keychain → certificate assistant → request a certificate from a certification authority → enter account name B and email address → open the Apple developer page with account B to log in and download the “certificate request file "to the" create a developer certificate "section and the" create a distribution certificate "section. The " Developer Certificate " accepts the name from account B successfully, but the " distribution certificate " accepts the name of account A. I revoked the certificates from account A and account B. I removed the certificates from the access profiles and key profiles for the keys from the organizer xcode and developer page, but still I can’t create a distribution certificate with the name of account B. I have to send my application from account B because I created the application on " itunesconnect " and I want to show the name of the developer as account B. To What is the account distribution certificate for account B ? take the name account name B instead of account name A ? What is the problem?

Answer 1

Account A and B do not have the same team name? Because the development certificate is for the team member and Cert Distribution. for the team. So, if you have the same team name for both accounts, the distribution certificate will have the same name.

Answer 2

You can create additional keychains for certificates when you have several programs for developers. Configure one set of certificates for each keychain you add.

Xcode will only read certificates by default keyword. Therefore, when you want to work with a set, copy the certificates from your secondary keyring to your default keyring (login). Then move them back when you are done.

This is a less than ideal solution, but it was an Apple solution.