Pere Argelich Romà
Apr 02, 2024 10:21 PM
In the new version 25.1.38, if the document is not modified, it can be saved and loaded correctly, but if you mark some field as required and save the document, then you can not open it again... in the javascript console you get this error.
Image_7067_1712076525142
Steps to reproduce the error:
1. Open the following link: https://stackblitz.com/edit/ns6rcb-vwlrdt?file=index.js,index.html
2. Click on the folder icon (Open file) and open the PDF document attached to this message. Select a field and check the required box.
3. Click on Download the document and save it on your PC.
4. Click on the folder icon (Open file) and open the PDF document we saved in step 3.
5. Does not open.
Hi Pere Argelich,
We
were able to reproduce the reported issue "Exception occurred on resaving modified PDF” and suspect this to
be a defect. We will analyze further on this and update you with more details
on April 5th, 2024.
Regards,
Sathiyaseelan K
Hi Pere Argelich,
We
have forwarded this issue to the relevant team, and they will validate it. More
details will be provided to you by April 8th, 2024.
Regards,
Sathiyaseelan K
Hi Pere Argelich,
We
apologize for the inconvenience. We are currently prioritizing the validation
of this issue with high priority to identify the exact cause. We will provide
an update regarding the issue fix within two business days.
Regards,
Sathiyaseelan K
Hi Pere Argelich,
We have confirmed the issue "Exception occurred on resaving modified PDF" and logged it as a defect. The fix
for the issue will be available in our upcoming weekly NuGet release on May 8th, 2024. You can track the status of the
issue through the following link.
Feedback link: Exception occurred on resaving modified PDF | Issue Feedback
Disclaimer: "Inclusion of this solution in the weekly
release may change due to other factors including but not limited to QA checks
and works reprioritization."
Regards,
Sathiyaseelan K
Hi Pere Argelich,
Sorry for the inconvenience. We did not
include the fix for the reported issue “Exception
occurred on resaving modified PDF” in our recent weekly release due to the complexity of the issue the
fix will be available in the upcoming weekly release on May 15th, 2024.
Regards,
Sathiyaseelan K
Hi Pere Argelich,
Sorry for the inconvenience. We did not
include the fix for the reported issue “Exception
occurred on resaving modified PDF” in our recent weekly release due to the complexity in finding precise
root cause of the issue the fix will be available in the upcoming
weekly release on May 22nd, 2024.
Regards,
Sathiyaseelan K
Hi Pere Argelich,
Sorry
for the inconvenience. While addressing the reported issue, we discovered that
it affects both the PDF Viewer and PDF Library, making it more challenging to
resolve. We are prioritizing this fix and will include it in our upcoming
weekly release on June 12th, 2024.
Regards,
Sathiyaseelan K
Hi Pere ,
We apologize for the inconvenience. We have addressed the reported issue, but due to the 2024 Volume 2 main release code freeze, the fix was not included in the latest volume release. However, the fix for the reported issue will be incorporated in our upcoming weekly release on June 19, 2024.
Regards,
Sathiyaseelan K
Hi Pere Argelich,
Sorry for the inconvenience. The reported issue occurred on both the PDF Viewer and PDF Library sides, causing additional challenges in resolving it. We are actively working on fixing this issue, and the fix will be included in our upcoming weekly release on June 26, 2024.
Regards,
Sathiyaseelan K
Hi Pere Argelich,
We apologize for the
inconvenience.
The input document
is encrypted, and handling issue fix within saving the PDF as incremental
updated and archived stream is more complex than expected. As a result, we are
unable to complete this issue within the original timeline. We are prioritizing
this issue and will include the fix in the upcoming weekly release on July 3, 2024.
Regards,
Sathiyaseelan K
Hi Pere Argelich,
We have fixed the reported issue "Exception occurred on resaving modified PDF" and the fix for the reported issue was included
in our latest weekly release v26.1.40. Kindly upgrade to that version to
get the issue resolved.
Root cause: During an incremental update, once the number of objects surpasses
100, subsequent object values are consolidated into a single archive stream,
leading to the loss of form fill values preservation.
Solution: After an incremental update, archive stream objects are now
segmented, with up to 100 objects written per archive stream.
Packages:
Regards,
Sathiyaseelan K
Thank you!
Hi Pere Argelich,
Thanks for the update. If you are still facing any issues, don't hesitate to
reach out for further assistance.
Regards,
Sathiyaseelan K