I have tested the scenario using Aspose.Pdf for .NET 6.9.0 where I have tried extracting the bookmarks of one of my sample PDF documents and I am unable to notice any problem. Can you please share which version of Aspose.Pdf you are using ?
In case you are using v6.9.0, then we will be requiring the sample PDF document causing the problem so that we can test the scenario at our end. Please note that until or unless we are able to reproduce the problem at our end, we might not be able to get it resolved at our end. As the source PDF files are confidential, so I have marked this forum thread as Private so that no one else other than Aspose staff can access these files. In case you are still not comfortable, you may also consider sending the files directly to us. Please visit the following link for further instructions on How to send a license?
Since the problem is occurring for only one document, so I believe its something related to a specific file. As requested earlier, can you please share the source PDF document so that we can test the scenario at our end. We are sorry for your inconvenience.
Which part of “this is a tax document and you cannot see the file” do you people not understand?
Hello Tim,
I can clearly understand that the document contains confidential information but we require the document for testing purpose. Please note that we only use documents/files for test/debug purposes and once the testing is complete, these files are removed from our system.
tn77:
You have access to the source code. Find where the error message is and what causes it, and then get back to me.
I already have shared that during my testing, I could not notice this problem with one of my sample PDF files and also you have stated that the problem only occurs for one particular document. So how we can be sure that the same source code works for all documents and causes problem for particular file, unless we analysed that document. It's specific to the structure/complexity of that file.
Anyways, I will further discuss this matter with development team to get their input over this matter. We are really sorry for your inconvenience.
Yes, of course it is specific to the file. I mentioned that in the first post.
All that is currently relevant here is the error message. You have the source code so you should know where that message occurs. You should then know what might cause that error. Based on that, you should be able to tell me what is wrong with this document.
I have already requested the development team to try figuring out the reasons of this problem, based on error description. As soon as I have some updates over this matter, I will let you know. Please be patient and spare us little time. We are sorry for your inconvenience.
Our development team was able to find out the code portion where this exception is being thrown and we are going to share a HotFix with you. Please note that currently the HotFix is going through the Testing process and soon it will be provided for your review. Please be patient and spare us little time. We are sorry for this delay and inconvenience.