v2.6.4

Add error reporting to write{File,Folder}AtPath:...

These functions would return whether they were successful based solely on whether _zipOpenEntry() was successful. However, they did not consider whether zipWriteInFileInZip() or zipCloseFileInZip() could have an error.

Improved these functions so that any errors that are encountered are returned in a new output error.

In addition to being exposed publicly, these functions are called from other places in ZipArchive. But, in an effort to keep the surface area of the API change to a minimum, those cases just pass NULL to outError and don’t receive the benefit of this improved error reporting.

v2.6.3

This release adds a new delegate method: zipArchiveDidEncounterEntityUnzipError

This more general delegate method replaces the overly-specific delegate method (zipArchiveShouldTreatCRCErrorAsFailureForEntityPath) added in the previous release (2.6.2). During unzip, this delegate method is called for any error which might be recoverable. And, the delegate can specify whether the unzip operation should abort or continue.

v2.6.2

This release includes the following:

• Avoid problems with writeData creating files with bad attributes
• Report CRC errors from unzipEntityName
• Added new API that returns all entity names in a zip archive
• Added ability for unzipping to continue after a CRC failure via a new delegate method

v2.6.1

Merge in v2.6.0 changes from upstream.

This changes the API that we were using: since whether zip64 is used is now determined automatically, based on file size, we no longer have API that lets us specify this explicitly.

This release also contains a fix that we hope will be pushed upstream. See ZipArchive#757.

v2.5.5

• Merge in v2.5.5 changes from upstream

v2.4.7

Merge branch 'unzip-data-bug-8' of https://github.com/oneeightyg/ZipA…

v2.4.6

Merge branch 'unzip-data-bug-8' of https://github.com/oneeightyg/ZipA…

v2.4.5: Add new method unzipEntityName:fromFilePath:error

Locates the "entity" with `name` in the zip file at `path` and unzips it, returning it as data. The entity must be a file – directories and symlinks are ignored. Password-encrypted entities are not supported.

v2.4.4: New writeFileAtPath method controls whether zip64 is used

This new method allows clients to specify whether the zip64 format should be used when writing the specified file. Other methods are unchanged: that is, they always use zip64.

New parameter for SSZipArchive: `useZip64`

The designated initializer for SSZipArchive can now take a `useZip64` parameter to determine whether all the files in the archive should be written with the zip64 format.

The old initializer (-initWithPath:) remains, and creates an archive that uses zip64 (as before).