Writing to custom properties of PDF files with Aspose.PDF 18.12 resulted in corrupting customer files, however merely opening and resaving them (also with 19.x) had the same result.
We have customers urgently requiring that Aspose not corrupt their files.
I have examples files but these cannot be uploaded to a public forum.
Thank you for contacting support.
Would you please share source and generated files along with narrowed down code snippet so that we may try to reproduce and investigate it in our environment. Moreover, the attachments are accessible to thread owner and Aspose Staff only so you may share the files. Or you may upload these to Google Drive, Dropbox etc. and then share download link with us privately through a message by clicking on my username.
Hi.
I supplied requested material last week.
What is the status of your investigation into this PDF corruption issue?
Thanks.
Thank you for getting back to us.
Would you please verify if you are facing the error as in attached screenshot with all of mentioned corrupted PDF documents so that we may proceed accordingly to help you out. Error.PNG
That is the error, yes,
Thank you for clarifying.
We have logged a ticket with ID PDFNET-46009 in our issue management system for further investigation and resolution. The ticket ID has been linked with this thread so that you will receive notification as soon as the ticket is resolved.
We are sorry for the inconvenience.
Dear @Farhan.Raza, Aspose is destoying PDF files. Is there any ETA on when this will be fixed? According to the original post, all it takes for Aspose to destroy a PDF file is to open the file and then save it — no changes to the file are required and Aspose destroys it anyway.
Can we please get an ETA on a fix for this file damage Aspose bug?
We are afraid that ETA is not available yet. We have recorded your concerns and will let you know as soon as any significant update will be available in this regard.
Regretfully, the issue is not yet resolved. However, we will surely inform you as soon as we have some definite updates regarding its resolution. Please give us some time.
We apologize for the inconvenience.
We regret to share that we cannot offer any timeline at the moment as the issue is not fully investigated yet. We have recorded your concerns and will surely consider them during the issue investigation. We will certainly let you know as soon as we make some significant progress towards ticket resolution.
We apologize for your inconvenience.
Dear @asad.ali,
This Aspose PDF file harm bug was reported on 5 February 2019. Aspose has confirmed that the bug is real.
Today is 26 March 2021.
It has taken Aspose two years to not fix this bug.
Please accept our humble apology for the inconvenience being caused due to this error. Please note that we have raised the issue to the next priority level in order to get it fully investigated and resolved. We will share an update with you as soon as the ticket is fixed. We highly appreciate your patience and comprehension in this matter. Please spare us some time.
We are sorry for the inconvenience.
Hey Asad, as per your previous comment, you mentioned that the issue was raised to the next priority level 30 days ago. Do we have an update from them on the issue reported? Even a timeline would help at this point.
Yes, the issue was escalated to the next level of priority and is currently under the phase of investigation. As soon as the investigation is complete, we will be able to share some news about resolution ETA. We will surely share updates with you in this forum thread as soon as we have some. Please give us little time.
We apologize for the delay and inconvenience.
The issues you have found earlier (filed as PDFNET-46009) have been fixed in Aspose.PDF for .NET 21.5.