Distribution certificates in the keychain app vs in xcode's "Manage certificates" dialog vs on developer.apple.com

Question

LabyrinthSolutions OP

Created Apr ’18

Replies 1

Boosts 0

Views 4.2k

Participants 2

If I log into developer.apple.com, I can see that my disctibution profile is going to expire in a few weeks time

So I generated a new one (in developer.apple.com) but can't see any way to add it into xcode

When I open up the "Manage certificates" dialogue in xcode, I can see the certificate which is going to expire, but clicking the "+" button and then clicking "iOS distribution" shows a message saying "You already have a current iOS Distribution certificate or a pending certificate request"

If I open up the keychain access app, I can see couple of iPhone Distribution certificates which have different expiry dates than the ones that I see on developer.apple.com or in xcode

So my questions are...

Do I need to import my newly generated distribution certificate into xcode?
Are the distribution certificates in the kaychain access app used in xcode? Why do they have different expiry dates?

Boost

Answer 1

guywithmazda OP

Apr ’18

I'm not an expert on this, but since you haven't received other replies, yet. I'll share my thoughts.

You state that you created a new distribution profile, but then start talking about distribution certificates. I'll assume you mean you created a new certificate. I think you can use the download button for the certificate on the developer web site, then import that into Keychain access. Then you can uncheck the Automatically manage signing option in your project or when exporting from the archive to force Xcode to use the newer certificate. Those other certificates you see in Keychain are probably older ones that have expired, or perhaps you have used multiple developer accounts in the past?

Remember to update your distribution profile(s) with the new certficate. On the developer site, edit the profile, choose the new certificate, and click Generate. Actually, Xcode's automatic signing features may take care of this now, but I'm not sure. I guess you could export an archive, then check on the developer page to see if the profile has been udpated to use the new certificate. If not, do it yourself.

0