PDFKit PDFPage.characterBounds(at:) returns incorrect coordinates iOS 18 beta 4

Question

Created Aug ’24

Replies 6

Boosts 1

Participants 2

PDFKit PDFPage.characterBounds(at: Int) is returning incorrect coordinates with iOS 18 beta 4 and later / Xcode 16 beta 4.

It worked fine in iOS 17 and earlier (after showing the same issue during the early iOS 17 beta cycle)

It breaks critical functionality that my app relies on.

I have filed feedback (FB14843671). So far no changes in the latest betas. iOS release date is approaching fast!

Anybody having the same issue? Any workaround available?

Answered by DTS Engineer in 809694022

Hello. Thank you for filing a bug report. I can confirm that the bug you filed remains open and under investigation.

Please continue testing your software in upcoming system software updates and beta releases and add updates to your bug report.

That's as much as policy permits I can tell you at this time. I'll comment on this thread again if I'm able to dig up any other details I can share.

Boost

Answer 1

khm2 OP

Sep ’24

Any news on this topic? Still not working in the latest betas.

0

Answer 2

khm2 OP

Sep ’24

The latest Xcode / iOS RC candidates still have the same issue that PDFKits PDFPage.characterBounds(at:) is returning incorrect coordinates for characters on the PDF page.

This breaks apps that rely on PDFKit to read char positions from PDF files!

It should be fixed by Apple before the final release of iOS 18.

0

Answer 3

khm2 OP

Sep ’24

iOS 18.1 beta 5 does not resolve the PDFKit PDFPage.characterBounds(at:) issue of returning the wrong character bounds.

0

Answer 4

khm2 OP

3w

iOS 18.1 beta 7 does not fix the this bug. Is this even confirmed as a bug in iOS 18.x?

Would be great if someone from Apple could confirm it is a bug and that it is in the backlog for getting resolved. Thanks in advance!

0

Answer 5

DTS Engineer OP

Apple

2w

Recommended

Hello. Thank you for filing a bug report. I can confirm that the bug you filed remains open and under investigation.

Please continue testing your software in upcoming system software updates and beta releases and add updates to your bug report.

That's as much as policy permits I can tell you at this time. I'll comment on this thread again if I'm able to dig up any other details I can share.

0

Answer 6

khm2 OP

1w

FYI, neither iOS 18.1 RC nor 18.2 beta 1 resolves the issue.

0