3 Replies Latest reply on Sep 22, 2015 12:59 PM by Toto RoToTO

    extension packager fails on mac

    brendanT Level 1

      When I use extension packager I am not getting the META-INF folder with the signatures.xml file and thus am unable to open my extension in a CC app. I've tried using ZXPSignCmd and I get a nicely functionioning .zxp file but it doesn't install to CEP/extensions. So I can set my path tokens for the install in packager but the signatures aren't included OR I can get the signatures in ZXPSign but not the path tokens.

       

      Is there a way to set path tokens in ZXP? or any thoughts on what I might be doing wrong in packager? is this a mac issue? I'm self signing for now.

        • 1. Re: extension packager fails on mac
          Toto RoToTO Level 3

          First you need to sign your extension:

           

          usage: ./ZXPSignCmd —sign ‘extension name’ ‘extension name.zxp’ 'key.p12' 'key password'

                      ./ZXPSignCmd —sign com.sample.myExtension com.sample.myExtension.zxp myKey.p12 myPassword

           

          Once done, you could use ExManCmd to install it.

          usage: ./ExManCmd  --install ‘extension package path’

           

          useful link: http://aphall.com/2014/09/cep-5-distribution-en/

           

          Thomas.

          • 2. Re: extension packager fails on mac
            brendanT Level 1

            Thanks Thomas,

             

            Signing the extensions can be done with Packager its just packaging in an unexpected manner. It may be that Packager is expecting an MXI file but as far as I've been able to find that shouldn't be required and, in any event, the documentation on MXI seems to be sparse.

             

            My work around is to package and sign with zxpSignCmd then change .zxp to .zip. Decompress and repackage the decompressed file with packager. Then I'm able to set the path tokens and I get a properly installing zxp.

             

            If zxpSignCmd allowed you to set the path I'd just use that...though I must confess I haven't tried using path tokens with it yet.

             

            regarding ExManCmd: I'm making this for others to use so I can't put them through a lot of hoops to get it working.

            • 3. Re: extension packager fails on mac
              Toto RoToTO Level 3

              Are you trying to build an hybrid extension?

              (That is why you are using .mxi file).

               

              if this is what you are trying to do, here is how I do.

               

              1- Sign and package HTLM extension using ZXPSignCmd.

                  You should have an 'myExtension.zxp'.

               

              2- create a directory and copy your plugins or whatever.

               

              3- create an mxi file:

                  https://helpx.adobe.com/extension-manager/kb/configuration-file-reference.html

                  some documentation useful to create it correctly.

                  In that file, you can describe destination folder for each element. 

               

              4-  you should have something like this:

                  - package

                        - cs_resources

                             - plugin 1

                             - plugin 2

                             - text 1

                             - text 2

                        - myExtension.zxp

                        - myExtension.mxi

               

              5- sign and package, one more time, using ZXPSignCmd.

               

              Now you should have your hybrid extension done.

              Use ExManCmd command line tool to install it.

               

              ps: after using ZXPSignCmd, you cannot change extension and modify the content. The sign won't be valid anymore.

                   And if you try to install it anyway, this won't work (using ExManCmd), just because the sign is invalid.

               

              Thomas.