PDFpen 6.3.2, which Smile still makes available for customers using OS X 10.7 Lion, 10.8 Mountain Lion, and 10.9 Mavericks, is signed with a certificate that expired long ago, and it has no trouble launching. In the past, the expiration of a code signing certificate had no effect on already shipped software. Code signing is a way of assuring users that an app comes from a known source and hasn’t been modified since it was last signed - it’s a way to prevent bad guys from attaching malware to legitimate apps. Greg said that the reason PDFpen crashed - even before it actually launched - was because Smile’s developer signing certificate from Apple had expired. Shortly afterward, all PDFpen and PDFpenPro users received email from Smile that apologized for the inconvenience, explained the problem briefly, and gave the same solution.įor more details, I contacted Smile’s Greg Scown, whose expansion of the email’s explanation shows just how involved the modern Apple development world has become. Replacing the old version with the new one restored PDFpenPro to full working order. Luckily, my first guess at a solution worked: all I did was download the new PDFpenPro 8.3.2 manually. PDFpenPro blew out on my MacBook Air as well, which struck me as odd - both it and my iMac had been running macOS 10.12.3 Sierra for some time, and the app had worked correctly on both Macs recently. I was surprised today when I launched PDFpenPro 8.3.1 to work on a PDF and it crashed instantly, well before the app had a chance to load. #1657: A deep dive into the innovative Arc Web browserįixing (and Explaining) PDFpen 8.3.1’s Crash on Launch.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |