Not all folders cause this, but it does happen consistently within certain folders. I sometimes get the "1" error message with the 1.35 version of ZipStream. Preferable as small as possible, if you can distil and reproduce the Oh, and could you send me a sample Zip that fails, if it doesn't contain Some ZIPs of ~90mb have been fine and this troublesome zip of 129mb isn't working. I have a feeling it has to do with zip size. I will send over files and code when I return to the office. I have done some testing and haven't narrowed this down enough to know what is happening. We're using ZipStream to allow downloading of mp3 albums. Can you create a failing zip with dummy data?Īlso, does the failing zip work on other tools just not the iOS Archiver?
Archive utility archive#
Using 1.30 of Zip.php, created files are unable to be opened by OSX's Archive Utility. Occational bit and byte is highly inefficient. Such a pain.having to reparse already compressed data to fix the Preferably by being able to tell the PHP gzip functions to stop being It is my hope I'll be able to isolate a definitive solution shortly. Especially as this is repeated for each encode block Into now) and which the OSX tool definitely don't want there just makes That requires an 5 extra bytes at the end of the stream, and which canīe safely removed, provided the header is modified (which I'm looking That there then is a slightly different header in deflate (off by 1 bit) Marker to be right after that end of stream. Valid start marker (PK) the OSX tool does not do that, and expects the Ignore the bytes between the end of the deflate stream, and the next The error you mention at the end is slightly different though, where Iĭon't remove a few superfluous bytes, where unzip tools are supposed to
Rude, but because from what I can gather, StuffIt is a better tool :) Had it been possible, I'd have told mac users to go "StuffIt", not to be The zlib output from PHP's gz* functions work everywhere else, just not
Archive utility mac osx#
The root cause is a mix between an odd behaviour of the deflateĪlgorithm in the PHP implementation of zlib, and a bug in the Mac OSX Way to work around it without having to implement my own zlib. I now know for certain where the problem is, I just have to figure out a I am aware of this issue, and are looking into it at the moment as a
0 kommentar(er)
