We like to inform that you may share files with us via dropbox link so that we may further investigate to help you out. Also please share complete sample code as well.
We are currently using a temp license to evaluate the functionality and are pressed for time to fix this issue and get a permanent license. Until this issue is resolved, we are unable to proceed forward. Any help that you can provide is highly appreciated.
I am open to downgrading to a previous version (if you suggest that does not have this issue) if that means that I can move ahead with the testing and finish the process. Please suggest a version number and a download link if you know that will be the quickest way to fix this issue.
We have tested the scenario in our environment and managed to observe the similar issues that you have mentioned. This scenario needs further investigation and for which we have logged an issue ticket as PDFNET-47482 in our issue tracking system. We will further look into details of it and keep you posted with the status of its correction. Please be patient and spare us little time.
Do you have some information on the timeline for this ticket that you can share?
Also does this ticket include both watermark and banner issues?11
On another note I was able to further look into the watermark issue. It seems that with PDFA/1A transparency is not allowed and the watermark in the files is transparent. That is causing the file to not convert. I have looked at another library and they make the watermark opaque and it works. With PDFA/2A the transparent watermark works fine.
I hope this helps to further narrow down the issue.
Yes, the logged ticket is about both watermark and banner issues. Furthermore, the ticket has been logged under free support model where issues have low priority and are resolved on first come first serve basis. The issue has been logged in our internal issue management system and I am afraid that you may not be able to access it. However, we will keep you posted with its rectification status as soon as we have some updates.
We have logged these details along with the ticket and will definitely consider it during issue analysis.