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

[BUG] partially corrupt PDF causes blank pages #480

Closed
samuel opened this issue Jan 12, 2022 · 4 comments
Closed

[BUG] partially corrupt PDF causes blank pages #480

samuel opened this issue Jan 12, 2022 · 4 comments

Comments

@samuel
Copy link
Contributor

samuel commented Jan 12, 2022

I have a partially corrupt PDF that works fine in other places I've tried it (e.g. Preview.app on mac, MyPDF, Acrobat), but when reading with UniPDF the first 3 of 4 pages are blank. Running it through mutool clean repairs it so it seems there's enough information to be able to properly read the document. Unfortunately, because it contains sensitive medical information (PHI) I can't share the specific file, but perhaps something can be gleaned from the errors output from unipdf. I will see if it's possible to get a PDF showing the same issue generated that doesn't have PHI.

[DEBUG]  core.go:336 Pdf version 1.7
[DEBUG]  core.go:587 Warning: Unable to find xref table or stream. Repair attempted: Looking for earliest xref from bottom.
[DEBUG]  core.go:1409 ERROR: Unable to find object signature (���1Ҡ��-�����YI)
[DEBUG]  core.go:1262 ERROR Failed reading xref (unable to detect indirect object signature)
[DEBUG]  core.go:1263 Attempting to repair xrefs (top down)

Also, I don't see a way to connect the ERRORs that are logged to the specific PDF that is being read since there can be multiple concurrent uses of the library. Is there any way to read a PDF in a more "strict" mode that returns an error from the read functions rather than logging and attempting repair? This way it would be possible to inform the user that their PDF is partially corrupt.

@github-actions
Copy link

Welcome! Thanks for posting your first issue. The way things work here is that while customer issues are prioritized, other issues go into our backlog where they are assessed and fitted into the roadmap when suitable. If you need to get this done, consider buying a license which also enables you to use it in your commercial products. More information can be found on https://unidoc.io/

@samuel
Copy link
Contributor Author

samuel commented Jan 12, 2022

Note we have a commercial license (under Spruce Health Inc) so perhaps there's a more appropriate avenue for getting support let me know.

Thanks.

@gunnsth
Copy link
Contributor

gunnsth commented Jan 16, 2022

@samuel Please use our service desk https://unidoc.atlassian.net/servicedesk/customer/portal/8 and contact [email protected] if there are any problems with access.

@ipod4g
Copy link

ipod4g commented Nov 16, 2024

@samuel Hello
Could we close this issue? I wasn’t able to find it in our customer portal.
If you need any further support or assistance in the future, feel free to:
Open a ticket through our customer portal: https://unidoc.atlassian.net/servicedesk/customer/portal/8
Email us at: [email protected]
Or create a ticket here.

@ipod4g ipod4g closed this as not planned Won't fix, can't repro, duplicate, stale Dec 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants