Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Expected a dict object" - blank pages appearing in PDF #831

Closed
meerkat-mary opened this issue Mar 14, 2024 · 3 comments
Closed

"Expected a dict object" - blank pages appearing in PDF #831

meerkat-mary opened this issue Mar 14, 2024 · 3 comments
Assignees

Comments

@meerkat-mary
Copy link

Hi @hhrutter,

I'm facing a peculiar issue and I'm not entirely sure if it's due to pdfcpu or something else, but I thought I'd mention it just incase. I have a PDF that displays blank pages sporadically throughout the document when viewed specifically in Adobe Acrobat Reader. When viewing the document in other PDF viewers such as Foxit Reader or Apple Preview, it displays just fine.

When opening the offending pdf in Acrobat Reader, it displays the following error Expected a dict object. Looking through various forums etc, it looks like it may be due to some internal structure that throws Acrobat Reader off. Unfortunately I'm unable to share the PDF file due to its sensitive nature which I appreciate isn't helpful in terms of debugging, however the PDF is made up of a concatenation of multiple smaller PDFs, the blank pages in the final document all correspond to a particular source file which contains an image based signature - so I suspect that original file is introducing the issue that makes its way into the final file that is stitched together by pdfcpu.

I'll try to recreate the issue using a non-sensitive file in the interim, but it'd be great to confirm if this is something that pdfcpu can protect against e.g. failing a validation check on the file, or automatically cleaning up this problematic structure as part of the optimising step?

Thank you very much,
Mary

@hhrutter
Copy link
Collaborator

Hello!
Any of your input files for merging may be the culprit.
Should be possible to narrow this down by recreating that particular merge repeatedly omitting one input file step by step.
I am happy to look into this - there is always a reason and a way to fix, you can get in touch with me via email.

@meerkat-mary
Copy link
Author

I'm unable to recreate the issue and I suspect it may be due to corruption in the file introduced at the customer's end, so for now I'll go ahead and close this issue. If I do manage to recreate it reliably, I'll get in touch with you via email. Thanks @hhrutter!

@hhrutter
Copy link
Collaborator

👍🏻 Sure thing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants