Already at the presentation of MacOS Sierra 10:12 there were some problems with PDF support, which could solve Apple a little later in 10.12.1. With 10.12.2 returned the error, especially when working with PDFs, back.
As Adam Engst in TidBITS reports, deal with the flaw in Apple’s PDFKit in MacOS Sierra for several months, the software developers who rely on Apple’s implementation of PDF support.
These problems result in the fact that one should be careful especially when editing PDFs in Apple’s Preview app.
Among others, these users, use the Fujitsu ScanSnap. Here you edit a PDF in Preview OCR text layer is deleted from the document.
Developers need to develop their own solutions
TidBITS quoted on the problems, for example, developers Mindwrap, Devon Technologies, EagleFiler, and Bookends.
So said Mindwraps Craig Landrum about that you have already submitted many bug reports with Apple, describing, among other profound problems in PDFKit.
Now It was hoped that the company from Cupertino is this fix in an upcoming version.
Christian Grunenberg, the developer of DEVONthink, sees the reason in Apple’s desire common ground in iOS to use and MacOS. However, this objective should be fallen victim compatibility.
Many previous functions are now beyond defective or no longer available. The result was that now even had to develop their own solutions except where this was possible.
Jon Ashwell, the programmer of Bookends, writes that you had to invest a lot of work in these detours. Previously functioning features were unusable with Sierra at once.
“Sierra 10:12 and 10.12.1 were bad but 10.12.2 was a disaster,” said Ashwell.
So Bookends crashed in PDFs from having contained comments. The problem was solved so far only the complete disabling PDF comments.
Ashwell has also been reported several bugs in Apple. Two of them were closed as already reported duplicates, in another case asked Apple to the affected app. Since the submission of that Apple has not been reported.
“I have never seen such a sad case of sloppy code and indifference at Apple,” said Ashwell.
Interestingly, Apple’s own Preview app less affected by the deeper problems in PDFKit, as the third-party software.
So was Michael Tsai not understand in Apple’s Preview, developers EagleFiler, some errors in PDFKit.
This could indicate that Apple’s team, which is engaged in the development of preview, the problem is aware but this circumnavigated only in its own app, rather than to solve in PDFKit itself.