ZXPSignCmd sign process is broken (segmentation fault)

For me everything works. I switched to http://timestamp.apple.com/ts01 long time ago.

System: macOS ARM.

I use this version of ZXPSign.

Result file has .zip extension, but tested .zxp and it works as well.

Command:

./ZXPSignCmd-64bit -sign "/path/to/extension" "/path/to/extension.zip" "path/to/certificate.p12" mypassword -tsa http://timestamp.apple.com/ts01

Confirming... still broken here too for the last few days.

Any news on this? We are having the same issue, signing works but only without timestamp. We are using a self-signed cert which expires in 2034. As far as I understand, it should be safe to omit the timestamp when the expiry is so far out. Can anyone confirm this?

I am experiencing the same issue and can't patch a bug since I can't sign an updated version of my extension. 

I am seeing exactly the same thing, looks like some Adobe service is not functioning correctly. A timely fix would be extremely welcome, because there is no alternative to ZXP Sign for distribution. 

Also seeing ZXP failures on all of our Windows and Macs both Intel and ARM, even with testing various TSAs, primarily DigiCert. Panels were building fine yesterday.

It doesn't seem that the executable cert has expired so I'm guessing some other internal mechanism is phoning home to some site that is down or using another verication that has expired or no longer works.

A timely fix is crucial for extension developers across Adobe apps to continue to update and publish new versions of their tools.

Additionally, long-term open sourcing ZXPSignCmd would be a smart choice so developers could temporarily patch issues like this on their own while waiting for offical fixes from Adobe.

Thanks for your help