Similar problem here. We have stopped all delivery, work on new productions, but some hundred thousand applications are still around with customers. @Adobe: It is a bad idea to check the "end date" of a timestamp! The timestamp's function is to keep the certificate valid. btw: There is no documentation saying that a timestamp itself will lose its validity - in many cases almost at the same time when the certificate period ends. Adobe must have seen the problem because current timestamps are issued until 2031 - out of reach for warranty claims. ... View more

general problem: Timestamps that were issued before 08 / 2015 were issued by Thawte. The period of validity of these timestamps ended with 30.10.2017. So all installations of older packages will fail. This is really a big issue. @Adobe: Workaround? (Of course you can set the system clock to 29.10.2017 - but that is no solution for our thousands of customers!) ... View more

Thanks for the fix. Now our customers are again able to install our products without calling the customer service. It's a relief. David ... View more

I have the same problem. Our certificates come from Symantec. They work without problems up to AIR runtime 20.0 on Mac OSX. When installing AIR runtime 21.0 all applications show an error message when installing: Publisher UNKNOWN. This applies to several versions of MacOS including the latest. ... View more