Extension signing

Another signing issue I've experienced was in the formatting of the cert file. I.e. after some update things just stopped working because some variation of the certificate file format/structure stopped being supported. The solution was to import the cert to browser(s) and try re-exporting it with different options until some worked.

Are you talking about getting panel to load on your test machine or distributing to other people? With CC 2015 the big issue is that it no longer works with Adobe Extension Manager, i.e. a valid .zxp in general does not install properly by double clicking it. It's quite confusing since AEM still opens the files and can copy somethings in right places depending how you made the .zxp possibly leaving Photoshop in a mixed state state of files.

My way of trying to maintain sanity

• Have scripts to clean up everything you might have installed
  • Windows
    
    • (Addons install location) \Program Files (x86)\Common Files\Adobe\CEP\extensions
    • ("normal" install location) C:\<username>\AppData\Roaming\Adobe\CEP\extensions
      
  • Mac
    • ~/Library/Application Support/Adobe/CEP/extensions
• Have scripts for copying development versions
• Have scripts for repackaging
• Before uploading to store create a test package that is not public but shared with you and verify all files get in right places
• When not store testing, uninstall your extensions from Adobe Addons site so CC does not resync files back to you

One specific point that might be your problem is that in debug mode Photoshop does not verify signature when loading panels. Not in debug mode it does and any leftover file in the folders will break this even with valid signature. Also the signature is in META-INF/signatures.xml and if you're testing by copying files then you get this by extracting the signed zxp

If still in trouble tell us

• Windows/Mac
• How do you "install"
• your .mxi/manifest.xml

I don't create extensions. I only created one using one of Adobe configurator and that did the signing for its Photoshop version.  Adobe Photoshop extension feature environment seems to change with each release of Photoshop and are not compatible. I rather just write Scripts and record actions that work in all Photoshop versions. Adobe is working on that to the new ScriptUI CC 2015 does not work like ScriptUI did in prior versions of Photoshop and has issues.

Did you do both ZXPSignCmd steps required for selfsigning

Creating a self-signed certificate:

./ZXPSignCmd -selfSignedCert US NY MyCompany MyCommonName abc123 MyCert.p12

This generates a file named MyCert.p12 in the current folder. You can use this certificate to sign your extension:

./ZXPSignCmd -sign myExtProject myExtension.zxp MyCert.p12 abc123

This generates the file myExtension.zxp in the current folder, adding these two files to the packaged and signed extension in the final ZXP archive:

• mimetype : A file with the ASCII name of mimetype that holds the MIME type for the ZIP container (application/vnd.adobe.air-ucf-package+zip).
• signatures.xml: A file in the META-INF directory at the root level of the container file system that holds digital signatures of the container and its contents.