-
Notifications
You must be signed in to change notification settings - Fork 80
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
Yauzl throws uncatchable error #65
Comments
It looks like you're not listening for the error event on the zipfile object. See https://github.com/thejoshwolfe/yauzl/blob/master/README.md#how-to-avoid-crashing |
Thanks, missed that part, added some code and will do some more testing... |
You are right, in that I had to listen to the error event.
However, how do I prevent this? I don't even mind skipping the file (its not a file I need), can I process the file further? |
Did you read the documentation? |
This issue has come up before in #54. A workaround for recovering from zipfiles corrupted in this way isn't documented in the readme, but maybe it should be. |
@PanMan can you tell what client is creating zipfiles with |
Please reopen if you have any other questions. |
Sorry, I missed this notification. We use Yauzl to process chat archives created by WhatsApp. It hasn't happened often, but did happen a few times. |
I am interested in reproducing the backslash filename problem. I have WhatsApp for android, and i've been looking into creating a chat backup of conversations. Is there any advice you can give me to help me reproduce this issue? There's no rush. I may not make any substantial progress on this issue for a few weeks. |
Backslashes are now silently converted to forward slashes as of 6a9e652 published in yauzl 2.10.0. |
yauzl throws this error that I seem to be unable to catch or prevent:
Am I doing something wrong? This started happening a few weeks ago, on very few files. Sanitizing file names doesnt seem to solve it.
The text was updated successfully, but these errors were encountered: