Attached is the same cert used to test with. The password is Mj5d6J8AyLm42Ris
cert.zip (1.9 KB)
Thank you for sharing the files.
We have tried to work with the code snippet shared by you but we are getting CryptographicException when commenting out the Catch statement before Finally statement. Attached is the screenshot for your kind reference Exception.jpeg. Would you please create a narrowed down sample application reproducing the issue so that we may proceed further to assist you.
I’ve never seen that error before as it should have worked. Anyways, I created a project for you. You need to replace the aspose license with yours, and add the asposepdf dll reference as well. I’ve taken care of the pfx and pdf file for you too to try to make it as plug and play as possible.
asposePDF.zip (264.9 KB)
Thank you for sharing requested data.
We have been able to reproduce the issue in our environment. A ticket with ID PDFNET-45262 has been logged 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.
Will the fix be made in the next release?
The ticket has recently been logged under free support model so it will be scheduled on its due turn which can take some months to resolve. We will notify you as soon as the ticket will be resolved.
However, we also offer Paid Support, where issues are used to be investigated with higher priority. Our customers, who have paid support subscription, report their issue there which are meant to be investigated urgently. In case your reported issue is a blocker, you may please consider subscribing for Paid Support. For further information, please visit Paid Support FAQs.
What is the status for this bug?
Thank you for getting back to us.
We are afraid PDFNET-45262 is still pending for investigations owing to previously logged and critical tickets. It may take few more months to resolve. We will let you know as soon as some significant updates will be available. We appreciate your patience and comprehension in this regard.
It’s been almost 7 months since this bug was acknowledged. I understand there are other issues, but it’s not like a new bug as this used to work in previous releases, but broke with subsequent releases at a specific release.
Thank you for being patient.
We are afraid this ticket is still unresolved owing to previously logged and critical issues. However, we have raised its priority to next level while recording your concerns. We will try to schedule it soon and will update you once resolved. Please spare us some more time.
This is approaching one year since this issue was acknowledged. This is seriously poor service as 3 months would be acceptable, but 9 months is just ridiculous. We purchased a new license because we want to upgrade to the latest version, but can’t because this issue exists.
Who do we need to contact to escalate this to be fixed as it used to work in a prior version.
We are sorry for this being still unresolved. Your concerns have been recorded and this ticket will be scheduled as soon as we can. Kindly spare us little more time. We really appreciate your patience and cooperation.
We believe we’ve been more than patient. Please fix this issue asap as your teams have had more than enough time to deal with it.
We apologize for the inconvenience faced.
Please note that we do understand severity of the issue for you and already have raised its priority to next level. We will definitely try to schedule its fix as soon as possible and share an ETA with you. We highly appreciate your patience and comprehension in this matter.
We are sorry for the inconvenience and delay.
It’s been almost a month since this was put on the priority list. We’re coming up to a year since the original ticket was opened, and the bug was acknowledged. Do you guys have an ETA?
Hopefully it’s not going to take another year.
We would like to share with you that your issue is already under investigation and it will definitely be resolved as soon as investigation of the issue completed. The analysis process is expected to be completed in next month and we will be able to share any reliable ETA once it is done. We really appreciate your cooperation in this matter. Please spare us little time.
We are sorry for the inconvenience.
Any updates on the ETA?
Thank you for getting back to us.
We would like to update you that the tentative ETA for resolution of PDFNET-45262 is Aspose.PDF for .NET 19.7 which is likely to be released around first week of July 2019. We will let you know as soon as it will be resolved. We are thankful to you for your patience.
The issues you have found earlier (filed as PDFNET-45262) have been fixed in Aspose.PDF for .NET 19.7.
Just tested it in the new version, and it has not been fixed.