Ah - yes, so the "save" operation is not available at that time, because you've kicked off an asynchronous operation which is still ongoing. Maybe we need a better error code for that...!

If you move the save call into the zipDone handler, it should work?

thanks

worked :)

What if we add multiple files one by one? will the Complete trigger each time?
Or how does it work?

Great

It's only functions that end in "Async" that have this limitation; adding other files is just done inline whilst the function call is happening, so we don't need to lock down the archive (basically it's to stop weird multithreading complications..)

Async functions are just:
ZipArchive.addFilesAsync()
ZipArchive.extractFilesAsync()

Ah - yes, so the "save" operation is not available at that time, because you've kicked off an asynchronous operation which is still ongoing. Maybe we need a better error code for that...!

If you move the save call into the zipDone handler, it should work?

thanks

Hi @ajwfrost , I get the same error message as @raresn, but calling the save function on the complete Event.
I believe it is an AIR memory allocation or garbage collection issue. I created folders of different depths and sizes
and observed the System.freeMemory ... If the size of the folder exceeds the free memory neither the progress
handler nor the complete handler is called and no exception is thrown. Any further trial of zipping a folder will then throw the above mentioned exception.
Info: My trial folders structure varied between a depth of 1 to 8 and a size between 60 and 100 MB.
Zipping folders < 64 MB succeeded almost every time whereby folders > 64 MB failed almost every time.

My environment:

AIR SDK 51.2.1.7
Flex SDK 4.16.1.20171115

OS:
Linux 6.14.0-24-generic
Ubuntu 24.04.2 LTS; glibc: 2.39
Desktop: ubuntu:GNOME

Actually createFromFolder is a synchronous operation.. useful for small sets of files perhaps; if you were operating on a folder with a lot of content, then best to use addFilesAsync.

They're basically doing the same thing, it's just that one of them is static hence also creates the object on which it then operates. But because createFromFolder() is returning an object, to which you'd have to add listeners to if it was asynchronous, there is a potential race that could happen where you may miss a 'complete' event if you've kicked off the process before adding the event listener.

We can add clarification in the documentation for the methods that are synchronous though, in case that helps. Would it also help to have a property saying whether an async operation is in progress?

Regarding an upload() method - ZipArchive can be purely memory-based, but I guess yes it would be possible to add that sort of capability, similar to https://airsdk.dev/reference/actionscript/3.0/flash/net/FileReference.html#upload() - this then would be an async operation again, so we'd lock the zip archive to avoid you changing it whilst it was being uploaded. (And to avoid confusion of what the "complete" event would mean...)

If you listen to the ProgressEvent whilst an ..Async operation is happening, you'll get progress - but it's in terms of files, rather than bytes, as we don't go through everything to start with to work out how big everything is..