Non-conformity in PDF/A conversion

[Jesús]

Hi:

Sorry to come back to this issue. But I keep checking validation errors in the PDF->PDF/A conversion. In this case with 2024-e-posters.pdf

I attach the original file and the converted one. I have verified the non-compliance with Adobe Acrobat and VeraPDF.

I have used the following code:

​//await Task.Run(() => mDocument.ConvertToPDFA(PdfConformance));

await Task.Run(() => mDocument.Conformance = PdfConformance);

Version of Syncfusion.PDF.Base : 

Thank you very much

Jesus

Attachment: Captura_de_pantalla_20251124_215617_300cf68a.png

[Jesús]

attach the original file and the converted one.

Attachment: 2024eposters_ccc496b6.pdf

[Irfana Jaffer Sadhik]

Hi Jesus

Currently we are analyzing on the reported behvaior with the provided details on our end and we will share the further details on November 27th, 2025.

Regards,

Irfana J.

[Irfana Jaffer Sadhik]

Hi Jesus,

We confirmed the issue "Conformance failed after converting pdf A2b conversion" as a defect in our product and we will include the fix in our upcoming weekly NuGet release, which will be available on  December 16th,2025.

 

Please use the below feedback link to track the status of the reported bug.

Conformance failed after converting pdf A2b conversion in WinForms | Feedback Portal

Disclaimer: “Inclusion of this solution in the weekly release may change due to other factors including but not limited to QA checks and works reprioritization

Regards,

Irfana J.

[Jesús]

Hi,    

A small observation. 

The error report indicates WinForms. In the thread I generated, it stated Platform: WPF

Control: PDF. The development was done with WPF.

Best regards

Jesús

Attachment: Captura_de_pantalla_20251127_161452_40a05a57.png

[Irfana Jaffer Sadhik]

Hi Jesus,

Thank you for your clarification. We will ensure that the solution addresses both platforms accordingly.

Regards,

Irfana J.

[Irfana Jaffer Sadhik]

Hi Jesus,

Since the Volume 4, 2025 release is scheduled for today, there will be no weekly release this week. The fix will be included in the next weekly release, planned for December 23, 2025.

Regards,

Irfana J.

[Irfana Jaffer Sadhik]

Hi Jesus,

Sorry for the inconvenience caused.

Due to concerns about stability, we were unable to include the fix in our last weekly update. We will ensure that the solution is included in our next weekly NuGet release, which you can expect on December 30th, 2025.

Regards,

Irfana J.

[Aribalakrishnan Govindasamy]

Hi Jesus,

Sorry for the inconvenience caused.

Due to concerns about stability, we were unable to include the fix in our last weekly update. We have resolved all the stability concerns and included the fix in the release branch.  It will ensure our next weekly NuGet release, which you can expect on January 6th, 2025.

Regards,

Aribalakrishnan G.

[Jeyalakshmi Thangamarippandian]

Hi Jesus,

 

We have included the fix for the reported issue where "Conformance failed after converting pdf A2b conversion" in our latest weekly NuGet release (v32.1.22).

Please use the below link to download our latest weekly NuGet:

NuGet Gallery | Syncfusion.Pdf.Wpf 32.1.22

Root cause: While converting PDFA, the reported issue occurred because the document contained multiple metadata streams. During the conversion to a conformant format, we had to create new metadata. When validating the document, the presence of multiple metadata entries caused confusion, which led to the issue.

 

Regards,
Jeyalakshmi T