Adding to existing zip causing corruption
Chris G, posted Nov 19th 2009 at 2:56PM
I’ve just upgraded to v1.6 and found that if I add a file to an existing ZIP archive, Springy displays the archiving parameters, you hit OK and everything seems to work fine, but then if you close Springy and try to open the archive it gives you the message:
Archive “name.zip” cannot be opened. The archive is invalid or of a type that Springy cannot handle.
Then the only program I can find that successfully opens the ZIP is WinRAR on Windows, and this displays all the files CRC32s as 00000000. This seems to happen whether the original archive was created with Springy or not.
Please let me know if this is a bug or something wrong with my system!
Not sure how clear I was being so I made this quickly, hope it helps!
http://www.youtube.com/watch?v=Qz4FX8PzQjk
Unfortunately, this IS a bug, and a very nasty and shameful one, I’d add. And it happens in Snow Leopard ONLY.
In the latest builds of the v1.6 I was experimenting with different states of ZIP archive while it’s being open by Springy, in order to make processing more efficient. If a ZIP archive is modified, all the changes to its central directory would be written only on closing it. My main (and development) platform is still Leopard, and after I made those changes I didn’t test them in Snow Leopard.
I turned out Snow Leopard handles document-based application termination in a different way than Leopard (and Tiger). So, if you just close archive by closing its window after modifying it, everything will be fine. But, if you quit the application before closing the document window, the corruption happens.
I’ll start investigating this different behaviour and fix it immediately. Meanwhile, I’ll remove the current build, so download link will be broken for some time. It will become valid once the new version (v1.6.1) with the fix becomes available.
You probably don’t want to hear this, but that is on my iMac running Leopard 10.5.8! Hope that doesn’t make it worse :|
Springy v1.6.1 is available for download. It (hopefully) fixes this very ugly bug. Chris, if you have any other similar problems, please let me know.
Just tested on my 10.5.8 system, all working fine now thanks :)
Oh and if you get bored you can check out the post I made suggesting some UI changes/options ;)
Thanks for the quick fix; works fine on my 10.5.8 system, too.
Snow Leopard is an utter disaster; I don’t ever plan to ‘upgrade’ to it unless I’m absolutely forced to. I don’t think I’ve ever been so disgusted with a new version of Mac OS; Leopard may well be the last version I ever install.
