Old Developer ID certificates stop on February 1, 2027. Here is what I would do this week
By Justinas Rolando, maker of MacPip
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:
- Packages:
.pkgfiles signed with a certificate issued from it will no longer install. - Signing: certificates issued from it can no longer be used to sign anything.
- Apps you already shipped: software that was signed and notarized with a secure timestamp keeps working, with nothing to do.
- Your next update: it needs a certificate from the newer authority, Developer ID Certification Authority (G2), plus a secure timestamp so it can be notarized.
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
- Anyone who ships a
.pkg: installers, drivers, audio plug-ins, menu bar tools with a helper, and anything an IT team deploys with an MDM. - Anyone whose updates go out as a
.pkg, through Sparkle or anything else. They are packages too. - Anyone who made their Developer ID certificate years ago and hasn't touched it since. Older Developer ID certificates lasted five years, so plenty of solo makers are still on one from the original authority.
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
- Apple Developer: Upcoming expiration of Developer ID Certification Authority (Sub-CA) (October 1, 2026)
- Apple Developer: Replacing Developer ID certificates issued from the previous Sub-CA
- Apple Developer: Certificates overview
- The Eclectic Light Company: Changing developer certificates might affect installers next year (October 16, 2026)
Keep reading
- Claude Fable 5.2 and Mythos 5.2: what's new, the benchmarks, and what it means for your MacClaude Fable 5.2 and Mythos 5.2 came out on November 9, 2026. Anthropic's benchmarks as charts, the prices, what changes on a Mac, and four free tools.
- Rosetta stops after macOS 27. Here is what I would check in my Mac appApple says macOS 27 is the last release with Rosetta for Intel apps, and macOS 28 keeps it only for some older games. How to find the Intel code hiding in your Mac app, and how people can see which of their apps are affected.
- macOS 27.3 makes Full Disk Access harder to get. Here is what I would change in my Mac appApple said on October 2 that granting Full Disk Access will take very explicit user action, and code in the macOS 27.3 beta stops denied apps from appearing in the list. What changes, who it hits, and what I would change in a Mac app now.
- Apple wrote down how App Review works. Here is what I would change before I submitApple published App Review help articles on review times, the Notes field, Bug Fix Submissions, appeals, screenshots, purpose strings and account deletion. What they say, and what I would change in a Mac app before I submit.
- The Swift Student Challenge takes Mac apps now. Here is what I would buildApple's Swift Student Challenge 2027 opens February 8 to 28 and, for the first time, takes apps for any Apple platform, macOS included. The rules, the dates, and how I would plan a Mac entry.
- macOS 27.2.1 stops curl trusting eMudhra. Here is what I would check in my Mac appmacOS 27.2.1, 26.7.3 and 15.8.3 remove five root certificates from /etc/ssl/cert.pem after the eMudhra key compromise. What changed, who it reaches, and what Mac app makers should test.
- Live Activities are coming to the Mac menu bar. Here is what I would do with my Mac appThe macOS 27.3 beta puts Live Activities in the menu bar of Apple silicon Macs, and Mac apps can start their own. What changed, the limits, and what to try first.
- Memory is making Macs dearer. Here is what I would do with my Mac appApple says memory will keep Macs short and pricier into 2027, and the cheapest Mac has 8 GB. Why that matters for your Mac app, and the checks to run this week.
- Apple now lets you talk to people who cancel. Here is what I would do with my Mac appSince November 4, App Store subscriptions can show a message or offer when someone cancels. The rules, what Apple says it does, and what to check on the Mac.
- Apple is adding two age rating questions. Here is what I would do with my Mac appFrom November 16, App Store Connect asks about shared location and dating features, and every app must answer by January 12, 2027. What changed and what to do.
- Siri AI is open to every developer now. Here is what I would do with my Mac appApple opened Siri AI to all developers in the macOS 27.3 beta. What changed, what you can and cannot ship yet, and a short plan for a small Mac app.
- Touchscreen Macs ship on November 6. Here is what I would check in my Mac appApple's first touch Macs arrive November 6. What changed, what Apple tells developers to do, and a short list of things to test in your own Mac app.
- Introducing MacPipWhat MacPip is, why I built it, how listing and launch day work, what a blue tick really means, and the real numbers from its first days.
- How to launch a Mac app: a checklist that fits on one pageWhat to do before, on and after launch day for a Mac app: signing, your page, directories, Product Hunt, Show HN and what to measure.
- How to write a one-line description that says what your Mac app doesA plain way to write the one line under your Mac app's name: name the job, cut the hype, and test it on someone who has never seen the app.
- Signing and notarization, in plain words, for people making their first Mac appWhat code signing, notarization and stapling each do, in what order, what your users see without them, and how to check your own build.
- What a dofollow link is honestly worth, from a site that offers oneWhat dofollow means, what Google says about links, why a link from a new directory is worth little today, and what to do instead of buying links.
Making apps for iPhone and iPad too? They have their own free home on iPip, MacPip's sister directory.