Bugs in PDFKit API?

I have some python and Swift scripts that set metadata in PDF files, such as Creator, Title, Author, etc.


They work in Sierra, but do not work on High Sierra. I’m presuming a bug in the API itself, given that both python and Swift produce the same result.

The code does not flag an error: a new PDF file is created, but no changes to the metadata are made.


The problem is with PDFDocument’s writeToFile:withOptions method. As far as I can tell, there have been no changes to the API.


Furthermore, PDFs created in High Sierra from “Save As PDF” (cgpdftopdf) produce syntax errors in Acrobat and GhostScript.

Acrobat reports “Incorrect value type for this key” when the “Report PDF Syntax Issues” preflight analysis is run.


GhostScript reports:

This file had errors that were repaired or ignored.

The file was produced by: Mac OS X 10.13.2 Quartz PDFContext


Has anyone else observed this?


Thanks


(PS. This post has sat waiting for "moderation" for over a week, because apparently the forum software didn't like repeated use of greater than signs and/or asterisks.)

Bugs in PDFKit API?
 
 
Q