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

'Something went wrong when processing your file" #10

Closed
maphew opened this issue Jul 20, 2023 · 4 comments
Closed

'Something went wrong when processing your file" #10

maphew opened this issue Jul 20, 2023 · 4 comments

Comments

@maphew
Copy link

maphew commented Jul 20, 2023

I get this error but there's no indication of what exactly when wrong or what troubleshooting avenues there might be. Any suggestions?

image

I tried with both Chrome and Firefox on Windows 10.

@hueyy
Copy link
Collaborator

hueyy commented Jul 20, 2023 via email

@maphew
Copy link
Author

maphew commented Jul 24, 2023

Thanks for the tip!

On intial page load I get:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static.cloudflareinsights.com/beacon.min.js/v2cb3a2ab87c5498db5ce7e6608cf55231689030342039. (Reason: CORS request did not succeed). Status code: (null).

None of the “sha512” hashes in the integrity attribute match the content of the subresource. The computed hash is “z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==”. view
Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content. web-client-content-script.js:1:407301
Uncaught (in promise) TypeError: t is undefined
NextJS 30
view-1b99a11ede18d1a6.js:1:4838
Loading failed for the <script> with source “https://gc.zgo.at/count.js”.

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.

@hueyy
Copy link
Collaborator

hueyy commented Jul 27, 2023

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.

@maphew
Copy link
Author

maphew commented Jul 31, 2023

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.

@maphew maphew closed this as completed Jul 31, 2023
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

2 participants