Unable to expand. It is in an unsupported format

I can’t install it or open it.
I’m on a macOS Ventura 13.4.1 using Local by Flywheel 7.0.1+6387
Clean fresh wp install with no other plugins, Twenty Twenty-Three theme and a child theme.

Hi @hb82 can you please try again while the site is on a different server and see if the downloaded folder can be opened. You can add the test site to https://instawp.com/ for free or any other server of your choosing.

Hi, I’m experiencing the same issue when cloning a theme. It won’t install or expand. When I try to install it, I get the following: “The package could not be installed. PCLZIP_ERR_BAD_FORMAT (-10) : Unable to find End of Central Dir Record signature“. When trying to expand the ZIP I get this: “Unable to expand. it is in an unsupported format.“
No problems at all exporting the theme, just cloning it. Seems to have started happening after updating to 1.13.0.

Hi @hb82 just checking in on this one, did you manage to download the zip when the site is on another server?

On your current server can you confirm that the server’s PHP install has the?libzip. Previously the plugin developers said that this plugin won’t work without support for these specific two functions: addEmptyDir() and addFromString(), which are part of that PHP extension.

https://www.php.net/manual/en/zip.requirements.php

@kingchris can you please check for the same as well.

If that doesn’t work please feel free to share a link to the zip files downloaded and I will test them on my end.

@thelmachido It’s working fine for me on a remote server, just not on my local environment. My local PHP install has Libzip version 1.9.2.

@thelmachido sorry for late reply. It works from a different server, but not from my local server using local by flywheel. The PHP version is 8.1.9 and libzip version 1.9.2 is enabled, but unable to open or install zip files when exported as “create a sibling of my child theme ” or “Create child of Twenty Twenty-Three” same problem as kingchris.

Hi, thanks for reporting this problem. It should be already fixed in the latest version of the plugin (1.13.1). Please update it and try again.

Everything is working fine now. Thanks!!