Lucid for Developer portal error: zip END header not found [no file] while uploading package

Hey ​@bhupesh68, thanks for raising this.

Our team is looking into this now and will get back to you shortly. The package bundle command and upload does work on linux based operating systems if that is available to you in the interim.

 

HI ​@chasefreeman  I also tried on Linux with no success. In fact, I used a standard cookie-cutter example from Lucid’s GitHub repo, tested it, bundled it, and uploaded it to the Developer Portal but still got the same error. 

Can you provide the exact command you are running as well as what sample extension from the github repo you tried to bundle? It is possible one of the sample extensions is out of date. Any other relevant information you could provide about operating system, extension sdk version, etc… might be useful to help us narrow down what is happening.

For reference, I was able to successfully bundle and upload the `example-card-integration` on Linux as of an hour ago.

Please the details requested: 

Interesting. We still are unable to reproduce the error. 

Would you be willing to upload the bundled sample extension from our public repository after running that command so we can investigate the contents?

Example Package  Please see the attached package for your reference.

Thanks, we will investigate and I’ll update this thread when we know more.

Hi ​@chasefreeman Is there an update on this use please.

Hey ​@bhupesh68, 

We’ve been able to identify that the difference between your package and one that we bundled and successfully uploaded. The difference being that the bundle you sent has an empty shape library file.

As to the why, we’re not certain. We’re still investigating, but don’t have an update for you as to why this is occurring. We’ve been unable to replicate the issue you are running into with bundling on any operating system. 

 

Thanks ​@chasefreeman  Since the code we’re exchanging is quite generic, could you share the version that’s working for you? I’ll test deploying that package on my end. If it works, it likely means the issue lies in how we’re bundling packages locally in our setup.