Aspose.PDF throwing Document information entry 'CreationDate' not synchronized with metadata property 'xmp:CreateDate' after updating package from 22.1.0 to 23.11.0

@GayatriNaik

We would like to share with you that the issue has been resolved and its fix will be included in 24.1 version of the API that will be published soon in January 2024. We will send a notification here once release is available.

Hi @asad.ali Hope its not Impacting the PDFA 3B Format size of File100X.pdf attached above coz its the major fix why we want to Upgrade to latest version coz with Old version , The File size after conversion was increasing 100 times almost from 350 MB to 14MB directly coz of which we increase Aspsoe.PDf version to 23.11 and faced this new Metadata isseu . So please test File size isseu too for File100X.pdf which imentioned earlier in details.

Also @asad.ali Is there any Particular date in Jan when this 24.1.0 will be released ?? when can i download it

@GayatriNaik

Your concerns have been recorded and we will surely consider them and test again for the File Size issue as well. Furthermore, we are performing some integration tests for 24.1 version and as soon as we are done, we will be able to share some particular date of release.

Thanks a I’ll wait for date and confirmation that file100x.pdf pdfa3b format will not exceed 720kb in lastest release

@GayatriB

Sure. Please note that your concerns have been recorded under the ticket already. However, we suggest and recommend that you post these concerns in the respective paid support ticket where your case has been escalated to the highest priority. You can have proper follow up and prioritize your case there.

Asad i can now see that the File100x.PDF file size is now showing 770 KB which was initially 13MB in lower version also. we need a firm confirmation that this changes are added in lower version too ??

@GayatriNaik

We are afraid that this cannot happen. We do not provide fixes or updates in the older versions of the API. Fixes and enhancements are made always in the higher and latest version(s) of the API. The fixes against your issue are delivered in 24.1 version and will remain permanent part of the API for higher versions. This is why we always recommend using the latest version of the API as it contains maximum fixes and the enhancements. In case you have further concerns, please let us know.

The issues you have found earlier (filed as PDFNET-56217) have been fixed in Aspose.PDF for .NET 24.1.