Hi Asad Ali,
Could you please update the status of the issue… It’s impacting our customer report.
Thanks,
Raj
We are afraid that the previously logged ticket has not been yet resolved due to other issues in the queue logged prior to it. However, we have recorded your concerns and will surely inform you as soon as we have some definite updates regrading ticket resolution. Please spare us some time.
We are sorry for the inconvenience.
Hi Asad,
Could you please update the status of the issue?
Thanks,
Raj
We are afraid that there are no updates at the moment regarding the ticket resolution as its analysis is not yet completed due to other pending issues in the queue. We will surely let you know as soon as we make some significant progress towards issue resolution. Please spare us some time.
We apologize for the inconvenience.
Any update on this?
Thanks & Regards
Raj
We are afraid that the earlier logged ticket has not been yet investigated. We will share updates with you as soon as it is fully analyzed and some ETA news is available. We highly appreciate your patience in this regard.
We apologize for the delay and the inconvenience.
Hi Asad,
Any update on this?
How long do I need to wait for this fix?
I’ve been waiting for more than 6months still not yet resolved.
Thanks,
Raj
The issue was logged under free support model where issues are resolved on first come first serve basis. The resolution time of the issue depends upon the number of issues logged prior to it as well as the complexity and the nature of the nature of the issue. We are afraid that we cannot share any timeline for the issue fix at the moment as it is not fully investigated yet. As soon as it is analyzed, we will be in a position to share some ETA. We highly appreciate your patience and cooperation in this regard.
We apologize for your inconvenience.
i have also noticed same issue,
The earlier logged ticket has not been yet resolved. However, we have recorded your comments and you will surely be notified in this forum thread as soon as the issue is resolved. Please spare us some time.
We apologize for the inconvenience caused.
ok, thanks for your response.
Any update on this? We are using paid license but the issue still persist…our customers are impacting due to this issue.
is there any different platform support for paid service?
Thanks & Regards
Raj
I have noticed that if cell value more than some character or size ( 1130 character) it’s creating the issue while generating pdf.
Please accept our humble apology for the inconvenience and the delay you have been facing. Please note that the issues in free support model are resolved on first come first serve basis as shared earlier. Also, the resolution time against an issue depends upon many factors including issue complexity and nature and number of API components need to be investigated. We also have paid support option that is provided to report issues that are needed to be fixed on urgent basis and they have highest priority in this mode.
Nevertheless, we have recorded your concerns and will surely inform you as soon as some progress is made towards issue fix. We again apologize for your inconvenience.
We have recorded this information under the ticket and will investigate the issue from this perspective as well.
The issues you have found earlier (filed as PDFNET-50624) have been fixed in Aspose.PDF for .NET 22.9.
Any update on this issue?
Thanks,
Raj
The ticket was resolved in 22.9 version of the API. In case you are facing this issue with latest version, please share your sample PDF and code snippet with us so that we can test the scenario in our environment and address it accordingly.
Thanks for your reply…
I didn’t receive any response from your team once issue gets resolved.
Will check and let you know the update.
You can check in this same forum thread that a notification was posted right after the release of 22.9 version of the API. There could be some issue that you did not receive it. Nevertheless, please feel free to test and let us know in case you face any issues.