I have been using the PDF Embed API on my website for a while now and it has been working perfectly until this past week. Here is a quick overview of my usecase so that you can better understand my problem.
1. I generate a new PDF file from a PDF template file on my Python backend via a few different open source PDF manipulation libraries.
2. The Python libraries allow me to fill in the PDF template file fields with some data. (The PDF template file is a an acrobat form)
3. After this my client side application loads the PDF embed SDK and renders the newly generated PDF form which allows users to continue editing the form fields.
This process has been working for me for several months and just this past week the PDF Embed SDK started throwing a new error. The error is being thrown from a Web Assembly file and is something along the lines of stating that the file is corrupt. The file loads fine into the PDF Embed iFrame but the form fields are no longer visible nor editable.
Nothing was modified on my server side and even older generated files which have already been edited in the PDF Embed iFrame are showing the same error. It seems that some code was changed on the Embed API side and I was wondering if this issue can be looked into and fixed. If anyone from the Adobe team has any information on this bug, I'd really appreciate it.
Copy link to clipboard
Hello, sorry to hear that you're facing this issue.
Please share a sample PDF which you're trying to render in Step 3. This will help us in debugging the issue.
Thanks for your response. I've attached a PDF containing a prepopulated acro form that will be readable and editable in a traditional PDF editing application as well as Google Chrome browser. However, as you will see, the form is not readable nor editable in the PDF embed due to an error thrown from one of the SDK's .wasm files. This was working fine just early last week, so any update on this to fix it, would be amazing.
Thank you for sharing the PDF. We have taken note of the issue and will try to resolve it soon. Please keep watching this space for updates.
Thanks for reporting the issue!
Just wanted to check in and see if there was any progress made on this.
This issue is already raised with the product team and we are trying to get this resolved soon.
Thank you for your patience.
Okay thanks, is there any sort of timeline on when we might expect for this to be released?
Bumping this up again. Is there any timeline on this?
Hi, just checking on the status of this fix. Has there been any progress made on this?
Sincere apologies for the delay in resolving this issue. We are working on this and will try to provide the fix as soon as possible. Thanks for your patience.
Any update on the progress with this? Just trying to get an idea on a timeline and if we need to start looking for another solution.
Apologies for the delay. We have started working on this and you can expect the fix to be available in next month's release. Thanks for your patience.
Thanks for the response, I am looking forward to the release!
We are actively working on the fix and will try to roll it out in the next month's release.
Thanks for your patience!
Hi Sumona, was this released?
It aint getting fixed broham.
Hi @DanC0dez, I'm really sorry for the delay in resolving this issue. We understand that this has been going on for a long time. We faced some unexpected issues while fixing this and hence the delay. Please know that we are working on the fix and will definitely try to release it as soon as possible, possibly in the next month.
Thanks for your patience!