JVM throws NullPointerExceptions on macOS Sierra 10.12 A few of the issues that we are currently addressing are listed below. We are actively working on identifying and resolving those issues. Java is compatible with this version, however, few Java issues have been reported on Sierra. MacOS Sierra was released by Apple in September 2016.
![]() Which Adobe Do I Need Sierra 10.12.6 Software And KnowDeveloper Craig Landrum, who founded the document management system company Mindwrap, said:The primary problem with Sierra with respect to PDFs is that Apple chose to rewrite the PDFKit framework in macOS 10.12 and it broke a number of things that PDF-related developers relied upon (I write scan-to-PDF software and know other developers who were impacted). Now, however, it seems Sierra’s PDF-related problems go deeper, and you should exercise caution when editing PDFs with Preview.The first I heard that Sierra’s PDF-related problems might affect more than ScanSnap scanners came in a comment left on one of those articles on 26 October 2016. Those problems turned out to be less severe than initially feared (see “ ScanSnap Conflicts with Sierra Easily Avoided,” 3 October 2016), and Apple resolved them in macOS 10.12.1 (see “ macOS 10.12.1 Sierra, watchOS 3.1, and tvOS 10.0.1 Mostly Fix Bugs,” 24 October 2016). #1577: iPhone 12/12 Pro repair program, fix corrupted Chrome extensions, iCloud Mail custom domains, Chipolo AirTag alternative, 10-digit dialing changesOne of the first problems with macOS 10.12 Sierra revolved around PDFs created by Fujitsu’s ScanSnap scanners (see “ ScanSnap Users Should Delay Sierra Upgrades,” 20 September 2016). #1578: Apple delays CSAM detection, upgrade Quicken 2007 to Quicken Deluxe, App Store settlement and regulatory changes Environment our designers are using Adobe CC 2017 on Sierra 10.12.6. Eric Bönisch-Volkmann, head of DEVONtechnologies, told me that they’ve spent a significant amount of development time working around Sierra’s PDF-related bugs in DEVONthink. However, throughout the next few months, additional complaints kept surfacing. There have been numerous bug reports sent to Apple on the several serious issues found with PDFKit and we hope Apple addresses them in an upcoming point release.Since Craig Landrum’s comment came after the release of 10.12.1 and the fixes for ScanSnap, I filed his criticism of PDFKit away as something that likely had been true but was no longer. It’s sad that basic functionality remains broken for so long — especially given that PDF was an area where Apple used to excel.More concerning, and this is what finally pushed me to track down all these reports and write this article, is that the recently released macOS 10.12.2 has introduced a serious new bug related to PDFKit. None have been fixed, as far as I can tell, and I’ve already filed two Radars for new issues in 10.12.2. It’s not only DEVONthink — a lot of other applications (such as EndNote, Skim, Bookends, and EagleFiler) are also affected.In fact, Michael Tsai, developer of EagleFiler, just published a blog post confirming his problems with PDFKit:I ran into a lot of PDF bugs in macOS 10.12.0. And there’s still work left to be done.10.12.2 introduces new issues (it seems that Apple wants to fix at least the broken compatibility now) and of course fixed almost none of the other issues. And to make things worse, lots of former features are now broken or not implemented at all, meaning that we had to add lots of workarounds or implement stuff on our own. However, it was released way too early, and for the first time (at least in my experience) Apple deprecated several features without caring about compatibility. Our customers are delighted.Although the DocumentSnap reader said that the problem didn’t affect PDFs scanned and OCRed with other solutions, Brooks Duncan was able to reproduce the problem with scans made from both ScanSnap and Doxie scanners he noted that both rely on the ABBYY FineReader engine.Sonny Software’s Jon Ashwell, developer of the Bookends bibliography app, expressed significant frustration as well, saying:We’ve been trying very hard to work around perfectly good code that was broken in Sierra. But yes, as soon as you edit a PDF in Preview the text layer is gone. We worked around the earlier bugs in DEVONthink 2.9.8 and will address 10.12.2’s new problems in the upcoming 2.9.9. Eric Bönisch-Volkmann confirmed this, saying ruefully:10.12.2 fixes a few bugs but kills the OCR text layer in PDFs. In another case, I was asked to provide our app, but after doing so there has been only silence. I’ve filed a number of radars with Apple, two of which were closed as duplicates. We’ve worked around that, but in the process had to shut down PDF annotations while we look for workarounds. If editing a PDF in Preview is unavoidable, be sure to work only on a copy of the file and retain the original in case editing introduces corruption of any sort. Michael Tsai said that some of the bugs he has seen don’t manifest themselves in Preview, suggesting that Apple’s Preview team is aware of the problems and is choosing to work around them rather than getting them fixed in PDFKit itself.It pains me to say this, speaking as the co-author of “ Take Control of Preview,” but I have to recommend that Sierra users avoid using Preview to edit PDF documents until Apple fixes these bugs. We have not had reports of PDFpen causing data loss of documents’ OCR layers.Interestingly, Preview itself may suffer less from bugs in PDFKit than third-party apps. Greg Scown of Smile told me that PDFpen operates independently of PDFKit, butBugs in Preview impact PDFpen customers whose document recipients use Preview rather than PDFpen to view or edit them. And issues reported by Peter Steinberger (author of the PDF framework PSPDFKit) were simply closed with the response that Apple didn’t intend to fix them.Apps that don’t use PDFKit are immune from these problems, of course, but only to the extent that their PDFs aren’t shared more widely and edited in Preview. For instance, PDF documents containing Eastern European characters created by the older ABBYY FineReader 8 engine are corrupted by PDFKit after editing. Full screen on virtualbox for macIt seems to work find in Sierra. I'm using Adobe Reader 11.0.18, which I think is the last pre-DC version. It's apparently up to version 15 now. For one thing their version numbers are a mess, with DC this and DC that. I try to avoid the Adobe Reader DC versions. I don't like the UI in the newer versions of Adobe Reader (it hasn't been Acrobat Reader for many years now, guys, but I guess old habits die hard). The CS 6 apps work OK in Sierra. But, since I'm not using Creative Cloud, I haven't yet been drawn into their airy-fairy ecosystem. If it ain't broke, don't fix it, which is sadly not part of either Adobe's or Apple's philosophical tool kit.It seems to me that the DC versions of Reader try too hard to get you to use Adobe's cloud services. But, like I said, old habits die hard. TidBITS is good enough to make them available in other formats, ePub for iBooks and Mobi for Kindle. Compared to you guys, though, my needs are pretty basic, like reading Take Control e-books.
0 Comments
Leave a Reply. |
AuthorSusan ArchivesCategories |