-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Invalid zip when installing extension #5897
Comments
If this helps, I was able to get some information about the error. The error happens in package-validator.js:extractAndValidateFiles. unzipper.on("error"... is called with the message below. [node-log 9:26:28 AM] decompress: [Error: Unsupported file type "SymbolicLink"] NodeDebugUtils.js:117 |
@MiguelCastillo How did you create the zip file? One of my extensions is having issues too. |
I always do the "Download Zip" from my github repo and push that... So, whatever github zip creation process does is out of my control. So, I load up the zip into the plugin registry and I also load using the url link; both have the same problem. |
So, I finally found the cause of the issue. DecompressZip chokes when processing files with type "SymbolicLink". Once I identified which ones were symbolic links, I deleted them from my repo and things are working again. Tips for debugging:
Happy debugging! BTW, I am not sure if there is a clean way to handle symlinks besides deleting them... Maybe there is an option we can pass into DecompressZip to ignore certain file types? -Miguel |
Nominating for sprint 35, on the assumption that symlinks might be common in some node use cases (since I think some node modules create things link symlinks into a bin folder?). I don't really know if it's that common though. |
I hit this again today trying to install this extension from url: https://github.com/jbalsas/brackets-apify |
This is now fixed on master, thanks to Miguel's pull request. |
I am trying to install one of my extension via the extension manager, and I get the "not a valid zip" error message. I was trying to debug brackets, but running the latest code keeps on closing my chrome instance; I am running brackets 33, which apparently needs an updated shell to run latest code.
This is the URL I am trying to install.
https://github.com/MiguelCastillo/Brackets-Tern
Same thing happens when I install from the registry. Any help would be great!
-mc
The text was updated successfully, but these errors were encountered: