Hi, I'm PipThese Featured apps take turns in my notch.
iPipSubmit
Blog

Old Developer ID certificates stop on February 1, 2027. Here is what I would do this week

By Justinas Rolando, maker of MacPip

Short answer

Apple's original Developer ID Certification Authority expires on February 1, 2027. From that date, Apple says .pkg installers signed with a certificate from it will no longer install, and its certificates can no longer sign. Apps already signed and notarized with a secure timestamp keep working. Check the issuer of your Developer ID certificates: Organizational Unit "G2" is fine, "Apple Certification Authority" means make a new one from the G2 Sub-CA and re-sign your packages.

If you sign a Mac app or an installer with Developer ID, there is a date to put in your calendar: February 1, 2027. That's about eleven weeks from today.

Apple posted about it on October 1, and it is easy to miss because nothing looks broken yet. Here is what changes, how I would check, and what I would do this week.

What Apple said

Apple's news post, Upcoming expiration of Developer ID Certification Authority, says the original Developer ID Certification Authority, the Sub-CA that sits between your certificate and Apple's root, expires on February 1, 2027. From then:

G2 is valid until 2031, but Apple says the certificates it issues expire every year. So this isn't a one-time chore anymore. It's a yearly one.

The package part is the sharp edge. Normally, Apple's certificates overview says a package with a trusted timestamp keeps installing after its Developer ID Installer certificate expires. This time Apple's own post says those packages stop. Howard Oakley at The Eclectic Light Company points out it isn't spelled out whether that covers every installer package, and what happens to disk images isn't settled either. I wouldn't wait to find out.

Who this hits

It's not only small apps. Out of curiosity I pulled the certificates out of a few apps on my own Mac. A big, well-known open source app had an update signed on November 10, 2026 with a certificate from the original authority. Another app was already on G2. So it's worth checking even if you think you renewed recently.

If you only ship through the Mac App Store, this is about Developer ID, which is for software you hand out yourself. It isn't about your App Store certificates.

How I would check

1. The certificate in your keychain. Open Keychain Access, select your Developer ID Application certificate (yours, not Apple's authority entry), open Issuer Name and read Organizational Unit. Apple's replacement page says "G2" means no action, and "Apple Certification Authority" means replace it. Do the same for Developer ID Installer if you have one.

2. A package you ship. Run pkgutil --check-signature on it. Look at the second certificate in the chain, Developer ID Certification Authority. If it expires on 2027-02-01, it's the old one. If it says 2031-09-17, it's G2.

3. An app you ship. codesign -dvv prints the same authority name for both, so it can't tell you. Run codesign -d --extract-certificates on the app in an empty folder, then openssl x509 on the files it writes. The commands are on the tool page.

I made a Developer ID certificate checker for this. Paste what pkgutil or openssl prints and it tells you which authority it is, by its Organizational Unit, its expiry date or its SHA-256 fingerprint, plus when your own certificate runs out and whether there's a trusted timestamp. It runs in your browser and nothing is sent.

What I would do this week

1. Make the new certificates. The Account Holder signs in to Certificates, Identifiers and Profiles, clicks the plus button, picks Developer ID Application, and when asked for the intermediary chooses "G2 Sub-CA (Xcode 11.4.1 or later)". Apple warns that any other choice might give you a certificate from the authority that's expiring. Repeat for Developer ID Installer if you make packages. If you are still on Xcode 11.4 or earlier, update first.

2. Keep the old one for now. Apple lets you hold up to five Developer ID Application and five Developer ID Installer certificates at once, so you can make the new one and test it while the old one still works. Don't revoke the old one. Apple's help page says software signed with a revoked Developer ID certificate can no longer be installed.

3. Switch your build. Update the identity in Xcode, your CI secrets, productsign, notarytool scripts and anything that picks a certificate by name. Both are called "Developer ID Application: Your Name", so a script can quietly keep using the old one. Check which one it used afterwards.

4. Re-sign every .pkg you still hand out. Not only the newest. Old versions on your download page, the installer your docs link to, the one in your support replies. Then notarize and staple again.

5. Put a yearly reminder in your calendar. New G2 certificates last one year. Future you will be grateful.

The MacPip angle

On MacPip, a listing links to wherever you ship your app, and a download that fails to install looks broken to people, whatever the reason. If you're getting ready for a launch, the notarization explainer reads the rest of your signing output, and listing your app is free. Listings are scanned automatically when they're submitted, and a blue tick only means MacPip checked the app on a date.

Sources

Keep reading

Making apps for iPhone and iPad too? They have their own free home on iPip, MacPip's sister directory.

Submit your appFree tools for makers