You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any good and quick way to verify if a given PDF file is not damaged? Even if for a damaged file PdfBox would produce a Java exception, this would be acceptable to me.
Why: In an Android app I use a different, C based PDF library, but I get a few native crash reports on Crashlytics, which are impossible to trace (probably some memory, C heap corruption...), and impossible to catch and handle gracefully. If some Java/Kotlin based method could verify and warn me that the PDF is damaged, I could reduce the number of bad crashes, and tell the user to get a fresh copy of that PDF file.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Is there any good and quick way to verify if a given PDF file is not damaged? Even if for a damaged file PdfBox would produce a Java exception, this would be acceptable to me.
Why: In an Android app I use a different, C based PDF library, but I get a few native crash reports on Crashlytics, which are impossible to trace (probably some memory, C heap corruption...), and impossible to catch and handle gracefully. If some Java/Kotlin based method could verify and warn me that the PDF is damaged, I could reduce the number of bad crashes, and tell the user to get a fresh copy of that PDF file.
Greg
Beta Was this translation helpful? Give feedback.
All reactions