Why this happens
When you try to Archive and upload to App Store Connect or validate for TestFlight, Xcode shows:
Failed to locate or generate matching signing assets
Missing iOS Distribution signing identity for ... Xcode can request one for you.
Even if your iOS Distribution certificate itself has not expired and appears in your developer account, Xcode still reports it as missing. This is not a problem with your distribution certificate or provisioning profile.
The cause is the Apple Worldwide Developer Relations Certificate Authority (WWDR) Intermediate certificate. Every Apple-issued developer certificate is issued by this intermediate, which in turn is issued by the Apple Root CA. Xcode and Keychain Access validate the whole chain. On February 14, 2016, the old WWDR Intermediate certificate expired.
If that expired intermediate is still in your Keychain, macOS treats any distribution or development certificate that chains to it as invalid. Xcode then cannot find a valid signing identity, even though the leaf certificate looks fine at first glance. The issue often appears after migrating to a new Mac and using Xcode’s Xcode > Settings > Accounts > Export Apple ID and Code Signing Assets or Export Developer Accounts. That export copies the expired WWDR certificate from the old machine to the new one, so both the login and System keychains end up with a copy of the expired intermediate.
Installing a new WWDR certificate alone does not fix it. As long as the expired copy remains anywhere in your keychains, the system will continue to prefer or validate against it and your identities will stay invalid.
How to fix it
You need to install the current WWDR Intermediate certificate and remove the expired one from both keychains.
1. Download and install the new Apple WWDR Intermediate Certificate
- Download the current certificate from Apple:
https://developer.apple.com/certificationauthority/AppleWWDRCA.cer - Double-click the downloaded
AppleWWDRCA.cerfile. This adds it to your Keychain. You can also drag it onto Keychain Access. - If prompted, choose to add it to the
loginkeychain. macOS will also make it available inSystemafter validation.
Do not revoke or recreate your iOS Distribution certificate yet. The distribution certificate itself is usually fine — it just needs a valid issuer to chain to.
2. Delete the expired WWDR certificate from both Login and System keychains
This is the step most people miss. There are typically two expired copies — one in login and one in System — and you must delete both.
- Open Keychain Access from
/Applications/Utilities/Keychain Access.app. - In the menu bar, choose
View > Show Expired Certificates. Without this, the expired WWDR certificate is hidden. - In the left sidebar, select the
loginkeychain, then select theCertificatescategory at the bottom. - In the search field, type
Apple Worldwide Developer Relationsto filter. - Look for
Apple Worldwide Developer Relations Certificate Authoritywith an expiration date ofFeb 14, 2016. It will show a redXorThis certificate has expiredstatus. - Right-click the expired certificate and choose
Delete. Confirm deletion. Be careful to delete only the expired intermediate, not youriPhone DistributionorApple Developmentleaf certificates and not your private keys. - Now select the
Systemkeychain in the left sidebar and repeat the same search and delete. You will need to enter your Mac administrator password to modify the System keychain. - Repeat for
System Rootsif you see another expired copy there, but the two main locations areloginandSystem.
If you see multiple WWDR certificates, keep only the one that expires in 2030 or later (the current one is Apple Worldwide Developer Relations Certificate Authority expiring in 2030). Delete any that expired in 2016.
3. Verify and restart Xcode
- In Keychain Access, with
View > Show Expired Certificatesstill enabled, verify that no expired WWDR certificate remains inloginorSystem. - Select your
iPhone Distribution: ...orApple Distribution: ...certificate. It should now showThis certificate is validwith a green checkmark and show the correct issuer chain when you double-click it and expand Trust. - Quit and reopen Xcode completely. Xcode caches signing assets on launch.
- Go to
Xcode > Settings > Accounts, select your Apple ID, and clickDownload Manual ProfilesorManage Certificatesto refresh. - Clean the build folder with
Product > Clean Build Folderand Archive again. TheMissing iOS Distribution signing identityerror should be gone and validation/upload should proceed.
4. If it still fails
- Clicking
Xcode can request one for youwill not help while the expired WWDR is present, because Xcode will generate a new identity that still chains to the invalid intermediate. Fix the WWDR first. - If you previously tried to work around the issue by revoking and recreating your distribution certificate, you will need to download the new provisioning profiles that use that new certificate after the WWDR is fixed.
- If Keychain still shows your distribution certificate as invalid after cleaning WWDR, delete and re-download the distribution certificate from the Apple Developer portal and double-click to install it again. Do not delete your private key for that certificate.
- A restart of your Mac can help if the System keychain does not update immediately.
How to prevent it
- Do not export and import the WWDR Intermediate certificate when moving machines. After migrating, always check Keychain Access for expired intermediates before archiving.
- Keep
View > Show Expired Certificatesin mind when debugging anyno valid signing identityorno matching provisioning profileserror. An expired intermediate makes valid identities look invalid. - When Apple renews the WWDR Intermediate (roughly every 7-10 years), install the new
AppleWWDRCA.cerpromptly and remove the old one from both keychains. - Avoid manually adding the WWDR certificate to multiple keychains. One valid copy in
Systemis enough; duplicates inloginandSystemmake cleanup harder. - Keep Xcode updated. Newer Xcode versions handle intermediate updates better, but they still respect what is in your Keychain.
FAQ
Why does my iOS Distribution certificate show as valid in the Developer Portal but invalid in Keychain Access?
Because validation is local. The portal only checks the leaf certificate’s expiration. Keychain Access validates the full chain including the WWDR Intermediate. If the intermediate is expired, the leaf is treated as invalid on your Mac even though Apple still lists it as active.
I installed the new AppleWWDRCA.cer but Xcode still says Missing iOS Distribution signing identity. Why?
Installing the new certificate is not enough if the expired one is still present. macOS can still find and use the expired copy. You must enable View > Show Expired Certificates and delete the expired Apple Worldwide Developer Relations Certificate Authority from both the login and System keychains, then restart Xcode.
Do I need to revoke my distribution certificate and create a new one?
No, not for this specific error. The distribution certificate itself is not the problem. Fix the WWDR Intermediate first and your existing distribution certificate will become valid again. Only revoke and recreate if the certificate itself is actually expired, revoked, or its private key is lost.
Parts of this guide are adapted from content licensed under CC BY-SA 4.0; this article is shared under the same license.
