As with PDFpen, downloading a new version with a current certificate should resolve the issue. Since Smile’s certificate was good for only a year, it’s likely that other direct-purchase apps with iCloud entitlements will run into this problem soon too. The problem appears to be unique to apps that have provisioning profiles and are sold outside the Mac App Store. Since the developer’s code never runs, macOS should recognize what’s going on and display an error message that encourages users to contact the developer. An app called taskgated-helper determines this even before PDFpen’s code runs, so there’s no way for Smile to detect the error condition and present an error to the user. Since PDFpen’s provisioning profile is also signed using Smile’s code signing certificate, the expiration of the certificate rendered the provisioning profile invalid. For PDFpen, the entitlement that’s being granted is the capability to access iCloud despite being sold directly, rather than through the Mac App Store, a feature that wasn’t possible until about a year ago. What’s new with PDFpen 8 is that, in addition to being code signed, it has a provisioning profile, which is essentially a permission slip from Apple that’s checked against an online database in order to allow the app to perform certain actions, called entitlements. 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. #1630: Apple Books changes in iOS 16, simplified USB branding, recovering a lost Google Workspace accountįixing (and Explaining) PDFpen 8.3.1’s Crash on Launch.#1631: iOS 16.0.3 and watchOS 9.0.2, roller coasters trigger Crash Detection, Medications in iOS 16, watchOS 9 Low Power Mode.#1632: Apple Card Savings accounts, SOS in the iPhone status bar, Tab Wrangler, Focus in iOS 16.#1633: macOS 13 Ventura and other OS updates, 10th-gen iPad, M2 iPad Pro, 3rd-gen Apple TV 4K, Apple services price hikes.#1634: New Messages features, Apple Q4 2022 results, Preview drops PostScript, iOS/iPadOS 15.7.1, Dvorak on iPhone and iPad.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |