For businesses that distribute Mac software outside the Mac App Store, Apple’s Developer ID certificate change is a continuity issue rather than merely an engineering task. Apple says certificates issued by its original Developer ID Certification Authority will stop working on 1 February 2027. The immediate concern is whether an organisation distributes affected installer packages or expects to release Mac software updates after that date.
What will and will not be affected
The impact depends on what is being distributed. Apple states that .pkg installer packages signed with an affected certificate will no longer install from 1 February 2027. That can create a visible interruption for customers, staff or partners who need a fresh installation of business software.
The position is different for Mac software that was previously signed, notarised and carries a secure timestamp: Apple says it will continue to work. This does not remove the need to consider future releases, however. Apple says future updates need a replacement certificate and a secure timestamp for notarisation.
Why this deserves business attention
Certificate ownership can be obscured when software is built or maintained by a third party. A business may own the product and customer relationship while a delivery partner controls signing, release access or renewal activity. If that responsibility is unclear, a time-bound certificate change can become a delayed release, an installation failure or an avoidable dependency on a supplier.
The commercial exposure is likely to be greatest where a .pkg installer is a primary route to distribution, where updates are contractually or operationally important, or where customers run managed Mac estates. The practical consequence is not necessarily an outage, but it is a reason to establish who can make and approve future releases before a deadline creates pressure.
Questions for product and operations leaders
- Do we distribute Mac software or .pkg installer packages outside the Mac App Store?
- Which legal entity or supplier owns the relevant developer account, certificates and release responsibilities?
- Do we have planned Mac software updates or new installer distribution after 1 February 2027?
- Which customer, internal or partner journeys would be affected if a new installation could not proceed?
- Is certificate renewal treated as an ongoing product-operating responsibility, rather than a one-off project task?
The longer-term operating consideration
Apple says the current Developer ID Certification Authority, G2, is valid until 2031. However, it also says certificates issued by that authority expire annually and must be renewed each year. For decision-makers, this means the replacement work should be viewed alongside a durable ownership and release-governance model, not as a single deadline response.
A useful outcome is clear accountability for software distribution, enough visibility to assess business impact before releases are due, and a maintained record of external dependencies. Where the product has changed hands, uses several suppliers or lacks an active technical owner, independent review may be appropriate before committing to future release plans.
Where Mac software distribution is part of a wider product estate, OUROPT can support app development work that clarifies release ownership and protects continuity as the product evolves.
Explore our services →Sources and references
- Upcoming expiration of Developer ID Certification Authority (Sub-CA)Apple Developer News · 1 October 2026