Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

Keychain says the push certificate has an invalid issuer

ErrorThis certificate has an invalid issuer

Short answer

Keychain marks a certificate as having an invalid issuer when it cannot build the chain up to a valid Apple root. The intermediate certificate that signed yours is missing or is the wrong generation. Install the Worldwide Developer Relations intermediate that expires in 2030, and for push certificates issued in 2022 or later, the G4 one.

  • Applies to macOS 15, Xcode 26, Apple Developer Program
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Open the certificate in Keychain Access, expand its trust chain and look at the Worldwide Developer Relations entry above it. Its expiration date and Organization field tell you which cause below applies. You can also list the intermediates installed on the Mac.

    security find-certificate -a -c "Worldwide Developer Relations" -p /Library/Keychains/System.keychain ~/Library/Keychains/login.keychain-db | grep -c BEGIN
  2. 2Match what you see, then jump to its fix

    1. 1The signing certificate was issued after 28 January 2021 and its chain shows an intermediate that expires before 2030, or no intermediate at allThe renewed Worldwide Developer Relations intermediate is not installedFix
    2. 2Only the Apple Push Services certificate is flagged, and it was created in 2022 or laterA push certificate needs the G4 intermediateFix

What does the error look like?

  • This certificate has an invalid issuer
  • Apple Push Services certificate shown as not trusted in Keychain Access

Cause 1 of 2

The renewed Worldwide Developer Relations intermediate is not installed

1Check

Apple renewed the intermediate. Certificates issued after 28 January 2021 are signed by the version that expires on 20 February 2030. Open Keychain Access, search for Worldwide Developer Relations and check the expiration date of each copy.

security find-certificate -a -c "Worldwide Developer Relations" /Library/Keychains/System.keychain ~/Library/Keychains/login.keychain-db | grep alis

2Fix

Download the intermediate from Apple's Certificate Authority page and open the file so Keychain Access imports it. Xcode 11.4.1 and later also fetches it by itself. Confirm that the installed copy shows an expiration in 2030.

# download the certificate listed on https://www.apple.com/certificateauthority/ (expires 2030)
open ~/Downloads/<downloaded-wwdr-file>.cer

3Verify

The certificate in Keychain Access no longer shows the invalid issuer message and its chain ends at Apple Root CA.

security find-identity -v -p codesigning

Confirmed by developer.apple.com

Did this fix it?

Cause 2 of 2

A push certificate needs the G4 intermediate

1Check

Apple's expiration notice says that for push notifications and passes, certificates issued after 27 January 2022 need the Worldwide Developer Relations G4 sub CA. Check that the intermediate in the chain has Organization G4 and an expiration in 2030.

# Keychain Access: open the intermediate, read Organization and Expires

2Fix

Download the G4 intermediate from the Certificate Authority page, import it, and keep the older copy installed until all of your servers and Macs have moved over.

open ~/Downloads/<downloaded-g4-file>.cer

3Verify

The push certificate now reads as valid in Keychain Access. Export it again if your push server needs a fresh .p12.

# Keychain Access: the push certificate shows no red cross

Confirmed by developer.apple.com

Did this fix it?

How do I stop it coming back?

  • Keep Xcode current: it installs the renewed intermediate on its own.
  • Install the same intermediates on every server and CI Mac that signs or sends pushes.
  • Note the expiry date of each certificate, since a revoked or expired certificate stops push delivery or App Store uploads.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Related fixes

Mobile apps

App record creation fails because you lack permission

You cannot add a new app in App Store Connect as a Developer or limited user

Only the Account Holder, an Admin or an App Manager can create an app record, and Apple blocks it until the Account Holder has signed the latest agreement.

3 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.