I have some elderly, unsupported Mac apps, and I followed the steps in this Stack Overflow article to retrieve their code-signed certificates and check their expiry dates.
This copied 3 certificates to a new location. The first ("Developer ID") has an expiry date of 25 February, 2022 (which has passed); yet the app still launches without complaint.
The second ("Developer ID Certification Authority") is dated 1st Feb 2027; and the third is Apple's root certificate, due to expire 9 February 2035.
My questions are:
Why didn't the app stop working (or why did the OS not flag any issue) in 2022?
Will it stop working in either 2027 or 2035 (all other things being equal), without some kind of manual intervention, such as ad-hoc local signing?
Asked by benwiggy
(39347 rep)
Apr 21, 2025, 11:41 AM