Is it happening with all kind of PDF files that you are processing? Can you please share one sample file with the code sample that is causing this exception? We will test the scenario in our environment and address it accordingly.
We were able to reproduce these errors in our environment with 25.8 version of the API. Therefore, below tickets have been registered in our issue tracking system for your PDF documents:
Ok, I understand. When do you think your team can resolve this issue? Can you provide any estimate?
Currently, our users are experiencing a lot of issues in our PROD environment. We need to evaluate if we have to address this problem with other options.
We are afraid that an estimate cannot be provide at the moment because the tickets are pending for initial analysis. The issues in free support model are prioritized on first-come, first-served basis and as soon as we complete the investigation, we will be able to share some ETA with you. The resolution time depends upon the number of issues logged prior to these tickets. We highly appreciate your patience and comprehension in this regard.
Is there any news? It’s been two weeks now, and our users have reported numerous issues. Please let me know if there are any updates regarding this matter.
We are afraid that the earlier logged ticket(s) have not been yet resolved due to other issues in the queue which were logged prior to this. Nevertheless, your concerns have already been recorded and we will surely consider them during the investigation process. We will inform you once we have some definite updates about ticket resolution. We apologize for the inconvenience caused.
We are afraid that no updates are available at the moment as investigation hasn’t been completed. Nevertheless, we will inform you once we have some certain news in this regard. We highly appreciate your patience in this regard.
Sadly, the tickets are not yet resolved. Once there are any definite updates regarding issue fix, we will let you know via this forum thread. We apologize for your inconvenience.
I wanted to check if there have been any updates on this matter. Could you please let me know if the investigation is still ongoing? Also, is there anything we can do to help expedite the process?
We are afraid that no updates are available at the moment. However, we will share updates via this forum thread as soon as we have some in this regard. We appreciate your patience in this matter. Please spare us some time.
Our users are still reporting multiple errors when handling PDF documents in our application in Production. I wanted to check if there have been any updates on this matter. Is there anything we can do to help expedite the process? Additionally, is there a way to prioritize this issue?
Unfortunately, the tickets remain unresolved due to other issues currently in the queue. As mentioned earlier, in our free support model, tickets are addressed on a first-come, first-served basis. The resolution time depends on the number of pending issues as well as the complexity and nature of the problem. Rest assured, your concerns have been recorded and will be taken into account during the investigation process.
If you wish to expedite this process, you can prioritize your tickets by opting for our paid support option, where issues are handled on an urgent basis. In the meantime, we will continue to update you on the status of the ticket(s) within this forum thread. We sincerely appreciate your patience and understanding and apologize for any inconvenience caused.
It’s been a while now, and the tickets are still open. No updates so far. Have you checked if the issues are still happening with the latest version of Aspose.PDF 25.10?
The issue is still happening with the latest version i.e. 25.10 because it hasn’t been rectified yet. We have raised the ticket(s) priority to the next level internally and once we have some ETA information, we will surely inform you. Your patience and comprehension is highly appreciated in this regard. We are sorry for the inconvenience.