iOS 11.2以下版本PDFAnnotation增删异常问题求助

Hey there, sorry to hear you're hitting this frustrating PDFKit bug on older iOS versions! I've run into similar compatibility quirks with PDFAnnotation pre-iOS 11.2, so here are some proven fixes and workarounds to try:

1. Force a Manual PDFView Refresh #

iOS 11.0.x often fails to automatically update the PDFView after modifying annotations. Try triggering a refresh explicitly right after adding or removing an annotation:

// After adding/removing the annotation
pdfView.setNeedsDisplay()
// For more stubborn cases, re-set the document to kickstart rendering
pdfView.document = pdfView.document

Sometimes pdfView.layoutIfNeeded() paired with the above can also help resolve layout glitches.

2. Validate Annotation Compatibility with iOS 11.0.x #

Certain annotation properties behave differently pre-iOS 11.2:

• Double-check that your annotation's bounds uses the PDF coordinate system (not screen coordinates) — older PDFKit versions are strict about this.
• Avoid using annotation subtypes or properties introduced in iOS 11.2 (e.g., some PDFAnnotationSubtype values like .ink with advanced settings).
• Ensure color and border properties use supported color spaces (stick to RGB for broad compatibility).

3. Re-Load the Modified PDF Document #

If the view still doesn't update, try serializing the modified document and reloading it:

guard let modifiedData = pdfView.document?.dataRepresentation() else { return }
if let updatedDoc = PDFDocument(data: modifiedData) {
    pdfView.document = updatedDoc
}

This is a heavier workaround, but it guarantees the PDFView renders the latest state of the document.

4. Implement Version-Specific Code Paths #

Wrap your annotation logic in version checks to handle older iOS versions separately:

let targetPage = pdfView.document?.page(at: 0) // Replace with your target page index
if #available(iOS 11.2, *) {
    targetPage?.addAnnotation(yourAnnotation)
    // Or targetPage?.removeAnnotation(yourAnnotation)
} else {
    // Low-iOS version handling
    targetPage?.addAnnotation(yourAnnotation)
    // Force refresh immediately after modification
    pdfView.setNeedsDisplay()
    pdfView.layoutIfNeeded()
}

5. Debug with Private Refresh Methods (Testing Only) #

For debugging purposes only (don't use in production code), you can trigger PDFKit's internal annotation view refresh:

pdfView.perform(Selector(("reloadAnnotationViews")))

This will confirm if the issue is purely a view-rendering problem rather than a failure to modify the document's annotation data.

Additional Debug Tips #

• Print the annotation count before/after modification to confirm the document's annotation array is actually being updated:

  print("Before: \(targetPage?.annotations?.count ?? 0) annotations")
  // Perform add/remove
  print("After: \(targetPage?.annotations?.count ?? 0) annotations")
  

• Check if PDFView settings like autoScales or displayMode are interfering with annotation rendering — try toggling these temporarily during testing.

If none of these work, it's likely an unpatched PDFKit bug in iOS 11.0.x. You can report the issue to Apple, and in the meantime, consider adding a minimum iOS version note or using a third-party PDF library as a fallback for older devices.

内容的提问来源于stack exchange，提问作者Maksym Musiienko