This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
ZIPs created via zip.js cannot be unzipped on older macOS versions with the default Archive Utility #467
Comments
|
Could you tell me if the file generated by this test works? It weights 422 bytes. |
|
I updated the code in order to use the Here is the code below: <!DOCTYPE html>
<html>
<head>
<title>Test zip.js (FS)</title>
</head>
<body>
<script type="module">
import * as zip from "https://deno.land/x/zipjs/index.js";
async function test() {
// Generate ZIP file
const fs = new zip.fs.FS();
const directory = fs.addDirectory("testdir");
directory.addText("content.txt", "test content");
const uint8Array = await fs.exportUint8Array({
dataDescriptor: false
});
// Download ZIP file
const blob = new Blob([uint8Array], { type: "application/zip" });
const link = document.createElement("a");
link.href = URL.createObjectURL(blob);
link.download = "test.zip";
link.click();
}
test();
</script>
</body>
</html> |
Repository owner
locked and limited conversation to collaborators
Dec 8, 2023
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Hi,
When a zip is created via zip.js and later tried to be opened on a user's machine which runs an older version of macOS, the default Archive Utility cannot unzip it as it results in an error. Any zip file created with the ZipManager demo is affected in the same way too.
The error is "Error 2 - No such file or directory" (in case of High Sierra and Mojave).
When unzipping it via the
unzipcommand, it works without an issue and I assume it would work with 3rd party unarchiver apps too, but our use-case cannot require that the user has such tool installed.When
zip -Fis ran on the zip file, it does not output any specific issues with the original archive, but the resulting archive can be unzipped via the Archive Utility:When looking at the original and the fixed zip via
zipinfo -v, I only see 2 differences:extended local headerisnoin the fixed file, while it isyesin the archive which was created via zip.jsNot sure if there's any other differences between the zip files as I could only extract this much information.
Here are the files which I've tested with:
Original zip created via zip.js, using the ZipManager demo: test.zip
File created via running
zip -Fon thetest.zipfile, on the machine which could not open it: test_fixed.zipI've tried to disable the
extendedTimestampand thedataDescriptoroption in our code which callsexportUint8Array, but it resulted in the same behaviour.Is there any way to get a resulting zip file which can be opened on these machines (so it matches the fixed zip file)?
The text was updated successfully, but these errors were encountered: