Skip to main content
D
DanC0dez
Participating Frequently
June 26, 2021
Question

PDF Embed API throwing corrupt file error from .wasm file

  • June 26, 2021
  • 1 reply
  • 4821 views

Hi all,

 

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.

 

 

      This topic has been closed for replies.

      1 reply

      S
      Adobe Employee
      Sumona Ghosh
      Adobe Employee
      June 28, 2021

      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.

      D
      DanC0dezAuthor
      Participating Frequently
      June 28, 2021

      Hi Sumona,

       

      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.

       

      thanks,

      Dan

      S
      Adobe Employee
      Sumona Ghosh
      Adobe Employee
      June 29, 2021

      Hi Dan,

      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!

       

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices