we’ve identified that our PDF rendering pipeline leverages the native CGPDFDocument APIs to convert PDF pages into images. However, in the latest release of iOS 18, the provided document fails to render even at the CGPDFDocument level.
Our analysis suggests that the issue may stem from the embedded custom fonts not being correctly processed in this version of the iOS platform. This appears to be consistent with several other reports and discussions around font rendering problems introduced in iOS 18, particularly involving subset fonts.
We’ve attached a collection of relevant community threads and references, including:
Apple Developer Discussion: Subset Font Rendering Issue in iOS 18
Given that our implementation is tightly coupled with Apple’s native PDF rendering APIs, this issue presents a blocking limitation for us.
With your permission, we would like to use this document as a sample case to formally report the issue through the appropriate Apple Developer forums and feedback channels.
Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports.
Bug Reporting: How and Why? has tips on creating your bug report.
