I had the same problem and wanted to ask if this ticket has been resolved? How is this going?
We are investigating the earlier logged ticket. However, can you please confirm if you are facing this issue with every PDF or with specific one? In second case, please share the sample PDF for our reference so that we can further proceed accordingly.
thank you for your reply.
We ran multiple tests and faced this problem for any, all PDFs.
The ticket PDFCPP-1769 is currently under the phase of the investigation and we have linked it with this forum thread. You will be notified as soon as it is resolved. Please spare us some time.
We are sorry for the inconvenience.
We would like to share with you that the issue has been resolved and its fix will be available in 22.7 version of the API which will be released soon.