Post

Replies

Boosts

Views

Activity

Reply to iOS 27: PDFDocument.dataRepresentation() writes corrupt 16-bpc annotation images (half the data missing)
Update: This issue still reproduces on the iOS 27.2 beta simulator when the app is built with Xcode 27.2 beta (iOS 27.2 SDK). With the same code (16-bpc image drawn in a PDFAnnotation subclass, then dataRepresentation()), the saved PDF is still corrupt: the image is declared as /BitsPerComponent 16 but contains only 8-bpc data, and the drawing is squeezed into the upper half of the page after reopening. So rebuilding with the latest SDK does not change the behavior. (The original issue on iOS 27.0 was confirmed on physical iPad devices; the 27.2 beta result is from the simulator.) The 8-bpc workaround (preferredRange = .standard) still works on the 27.2 beta simulator. I'm still looking for a way to keep 16-bpc output, if anyone has ideas. Feedback: FB25195006
Topic: App & System Services SubTopic: General Tags:
1w
Reply to iOS 27: PDFDocument.dataRepresentation() writes corrupt 16-bpc annotation images (half the data missing)
Update: This issue still reproduces on the iOS 27.2 beta simulator when the app is built with Xcode 27.2 beta (iOS 27.2 SDK). With the same code (16-bpc image drawn in a PDFAnnotation subclass, then dataRepresentation()), the saved PDF is still corrupt: the image is declared as /BitsPerComponent 16 but contains only 8-bpc data, and the drawing is squeezed into the upper half of the page after reopening. So rebuilding with the latest SDK does not change the behavior. (The original issue on iOS 27.0 was confirmed on physical iPad devices; the 27.2 beta result is from the simulator.) The 8-bpc workaround (preferredRange = .standard) still works on the 27.2 beta simulator. I'm still looking for a way to keep 16-bpc output, if anyone has ideas. Feedback: FB25195006
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
1w