Thanks for contacting support.
We have tested the scenario in our environment and were able to notice that the resultant PDF document was not PDFA compliant. Hence, we have logged an issue as PDFNET-43528 in our issue tracking system. We will further investigate the reasons behind this issue and keep you posted with the status of its correction. Please be patient and spare us little time.
We are sorry for the inconvenience.
Would you be so kind to provide us with status on the PDFNET-43528 issue?
We are glad to share that this issue has been resolved. Please use latest version of the API and in case you face any issue, please feel free to let us know.
Really sorry to inform you that the bug already has been verified with Aspose latest version - 19.11.
Please support us at your earliest convenience.
We are collecting the information which was extracted during resolution of this issue and it was specific to your shared document. We will share it with you shortly.