Well, that is problematic! I just tested mine and it worked on a test scan, so here’s hoping it is not quite as bad or as universal as made out. Otherwise that's going to be a real loss for productivity, I love my ScanSnap!
My guess is that it's not a guaranteed problem, but that they can't predict when it will happen. I imagine that if you check all your scans, you'll know if it bit you and can take steps to remedy the situation.
According to a further release from Fujitsu on the ScanSnap website (http://scansnapcommunity.com/features/14447-urgent-notice-for-mac-users-serious-issues-affecting-pdf-creation-and-editing-on-macos-sierra-may-cause-permanent-data-loss/
), they are working with Apple on a solution. It is unclear whether the problem lies in the PDF files ScanSnap creates or the way the PDF engine in macOS Sierra renders them. Seems like Fujitsu wants to point the finger at Apple but doesn't quite go that far.
This leaves open the question of whether a fix is going to have to come from Fujitsu or from Apple in the form of an OS update.
Given that the problem can appear on any PDF created by ScanSnap in the past, it seems like ScanSnap has been creating problematic PDFs for a long time, or Apple's newest PDF engine is not being as forgiving of file format variations as in the past.
Fujitsu hasn't answered the question of whether PDFs that are created by ScanSnap Cloud are affected. These PDFs are created without going through a direct connection to a Mac. They just get delivered to your Mac via whichever cloud service you choose.
Whatever the case, this is a show-stopper for me. I can't risk upgrading to Sierra until it's fixed.
Given Apple's continuing effort to lock down security on macOS, it just occurs to me that perhaps they did something to their PDF rendering that closed potential vectors for security vulnerabilities, but it had this negative effect on the way Fujitsu/ScanSnap was creating its PDFs. Just a thought.
Thanks for pointing to those new details from Fujitsu, Andrew!
The PDF rendering engine in macOS is a little funky — I know people at Adobe who are very unimpressed with it — but I've never heard of any issues along these lines before, which leads me to believe that Fujitsu is going beyond the basics of what macOS provides.
I've updated the article to note that VueScan works with the ScanSnap scanners in Sierra, so it might offer a useful workaround for ScanSnap users who need to upgrade to Sierra.
ExactScan also works with the Fuji SnapScan. Their driver also is faster in scanning than Fuji's own driver. For documents, ExactScan blows away VueScan for speed.
I wonder if previously scanned docs would be ok if opened in PDFpen/Pro. This is certainly a strange problem.
The implication is very much that they might not be OK.
Is it that clear? If the rendering engine in 10.12 is the problem, doesn't PDFpen have it's own engine? What about Acrobat/Reader? The info so far is very thin on how existing files become damaged...
By "clear," I meant from what Fujitsu has said. :-)
My strong suspicion is that Acrobat Pro is completely self-contained, but that most other PDF apps on the Mac rely at least in part on Apple's PDF engine.
The existing document incompatibility worries me. Aren't they just PDF files? If I use preview to open them will I have a problem?
If the underlying PDF format conflicts with Sierra's PDF engine, then opening with any app AND THEN SAVING could blank out pages. You can make changes in a PDF with Preview, so if you saved those changes, that could theoretically damage the documents.
You could always make a copy of the document in the Finder first, and then verify that every page is OK after you make and save changes. It doesn't sound like every PDF will experience the problem.
I use DevonThink Pro on Sierra. I don't use the ScanSnap organizing software, just the driver to perform the scan and route to DevonThink Pro. So far, I have seen no problems with this workflow, but will keep my eyes open!
So it seems most concerns were overblown? The Fujitsu update says the loss of previously scanned data is linked to their own management and editing software. And the new scanning problems are rather limited. Am I getting this right?
Yeah, after all their dire warnings, the problems seem pretty specific and easily avoided.