Zip plugin

Thank you!

I could build without any problems.

ZIP works well in all devices.

Hi @davida6.

What version of Corona are you using?

When (I need the complete date/time/timezone) on when you know it last worked and when it started failing.

What Device, OS and Version are you having the the problem on?

Thanks

Rob

Thanks Rob.

2017.3068

eastern time zone

I started on it about 3ish pm - and was working.  The night before it didnt.    About 11:00pm, last night, it stopped and I gave up on it about 12:30am this morning.

It worked on my first run this morning (about 9:30am) - same file that failed last night.

Various digiland and insignia tablets, OS: 5.1, 6.0

I am creating the zip file on a native app, and then bouncing it off a backend server.  The download gets the expected 200 response on the end phase, and the zip file resides in a subdirectory (with the same name as the file) I create off of the Documents directory.  The zip file name passed in the options is formatted as: “<subdirectory>/<filename>.zip”, and the zipBaseDir and dstBastDir directories are the Documents directory.  This puts the files in the proper subdirectory after the uncompress.  I had to do it this way as the uncompress did not properly build the sub-directory path for ALL zip files.  Some would, and some wouldnt.  Since I didnt control all of the creation of the zip files, this made them all end up in the right spot.

Thanks

Dave

Rob,

as of now, I have not had a failure today.

Thanks

Dave

We updated the plugin on Friday and then fixed an issue yesterday. I’m just trying to make sure you’re not caught up in those changes. But that fix was pushed earlier in the day yesterday. It sounds more like a file was getting corrupted along it’s upload/download path.

Rob

Got it. Thanks. 

On the plugin, any way to get some error reporting?  ErrorMessage and response are always empty. It would be nice to get something like: corrupted file, no room to expand, missing file, etc.  also, on a success, number of files would be nice in the response table. 

On a failure, knowing why would let us recover gracefully. 

Thanks

Dave

Just tried it out, it’s working for me now too. Thanks.