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
'Something went wrong when processing your file" #10
Comments
|
If you pop open the JS console via inspect element, a more detailed error
should be displayed. If you're comfortable sharing the file, I can also
look into this.
…On Fri, 21 Jul 2023, 04:54 matt wilkie, ***@***.***> wrote:
I get this error but there's no indication of what exactly when wrong or
what troubleshooting avenues there might be. Any suggestions?
[image: image]
<https://user-images.githubusercontent.com/486200/254987552-65039334-35fa-4414-962b-a663aeab6613.png>
I tried with both Chrome and Firefox on Windows 10.
—
Reply to this email directly, view it on GitHub
<#10>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABRYR4KRRAK3MV3SLRQRTPLXRGAX7ANCNFSM6AAAAAA2R4BGCU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
Thanks for the tip! On intial page load I get:
There are no further console messages after dropping the problem pdf into the page. On another pdf, which is a single page scan of signed document, the doc is processed correctly and there are no errors in the rendered page. Console has a warning of "Warning: decodeScan - unexpected MCU data, current marker is: ffff 2 pdf.worker.df7560ea.js:1:17818" Unfortunately I can't share the problem pdf. From my perspective this is no longer an issue as the situation which prompted me try Docdocgoose has moved on. However I'm happy to keep the file around a couple of days and share info from other troubleshooting steps if that would be helpful to the project. |
|
Hmm it does sound like an error thrown by pdfcpu, which DocDocGoose uses in WASM form. My guess is that there's some security feature on the docs that is impeding the decoding. This can be quite tricky to troubleshoot without the actual doc. Glad that it's no longer an issue for you. If you do come across this issue in respect of any docs you can share, do let me know. Also, feel free to let me know if you encounter any other issues. Thanks for raising this. |
|
Closing as it's not an active problem for me anymore. I'll reopen if it happens again and I can share a reproducible recipe or pdf. |
I get this error but there's no indication of what exactly when wrong or what troubleshooting avenues there might be. Any suggestions?
I tried with both Chrome and Firefox on Windows 10.
The text was updated successfully, but these errors were encountered: