Adobe embed API corruptFile error within rendition.js

[Adrian222744349dt5]

Ocassionally when using the Adobe Embed API, the API will successfully load a PDF and it's annotations, and then throw a "corruptFile" error from rendition.js (see attached screenshot). Rendition.js also console.logs undefined multiple times (also visible in screenshot). 

In the UI, the API shows an error indicating an issue with the client ID (see attached screenshot 2); this is despite the fact that it is a valid client ID that works most of the time, and the PDF and it's annotations were already loaded. Sometimes this error will be thrown after being able to view the PDF and annotations for up to 30 seconds. 

This issue can be reproduced more reliably in incognito mode with a PDF that has annotations. 

[Adrian222744349dt5]

Adding more info: I only received this issue for the first time during the last 1-2 weeks. 

[Joel_Geraci]

Can you share the PDF in question?

[Adrian222744349dt5]

Hi Joel

Apologies for the delay getting back to you. 

The issue seems to occur when the file 'Senator profileMainBriefFile (1).pdf' has the annotations in annotations.json applied. If I load the file without annotations it loads without issue. 

'Senator profileMainBriefFile.pdf' shows the file after annotations are applied. 

[Adrian222744349dt5]

Hi Joel

Just wondering if you have an update on this. This issue is still affecting us. 

[cfjedimaster]

Are you sure the annotations are valid? And does it consistently break with them or just off and on? Is it available online where we can see?

[Adrian222744349dt5]

Hi cfjedimaster

We are quite confident that the annotations are valid. I have attached the annotations and PDF to my previous reply. When adding these annotations to the PDF there are no validation errors. When adding invalid annotations in the past there have been validation errors. 

Additionally, the errors are being thrown from rendition.js, which makes me believe there is a bug or missing error handling there. 

[cfjedimaster]

Ok, thank you for the response. I've taken your source data, and this thread, and filed a bug report internally. 

[Adrian222744349dt5]

Thanks!