Problems installing my new extension

[karpiyon]

Hi,

I am testing my new extension.

Once everything was working i packed it as follows:

ZXPSignCmd -selfSignedCert <country> <city> <company> <commonName> 123456 selfDB.p12

ZXPSignCmd -sign <patghtoPanel> <zxpFile>.zxp selfDB.p12 123456

ZXP file was created but when i tried to install it i got this:

I tried to install another zxp from adobe exchange for photoshop and there where no problems.

My extension is for photoshop.

what can be the cause for this?

Why dose it now 'know' my extension is for PS? Where can i specify this?

Can there be anything missing in my manifest.xml? after all the panel is functioning as is should before packing.

it has this entry in it:

    <HostList>
      <Host Name="PHXS" Version="[14.0,99.9]"/>
    </HostList>

one more thing

How do you use the verify option for ZXPSigncmd?

I tried:

ZXPSignCmd -verify myzxp.zxp  |   <path to extension root>

That does run

Thanks

[Justin Taylor-Hyper Brew]

Have you tried installing manually? (rename .zxp to .zip and move that folder into your extensions folder)

[karpiyon]

Do you mean to move and unzip?

If yes than i did it and it is working fine.

I added this to my xml:

    <HostList>
      <Host Name="PHXS" Version="[14.0,99.9]"/>
      <Host Name="PHSP" Version="[14.0,99.9]"/>
    </HostList>

in addition i packed it with time stamp and it created the zxp file.

this time i got this error:

I used a selfSignedCert

[Justin Taylor-Hyper Brew]

Yes, I was referring to unzip and move. If you turn off playerDebugMode and your extension launches then it should be signed correctly and good to go, not sure why ExtensionManager wouldn't install it. Maybe try aescripts' ZXP Installer

[karpiyon]

I'll try it.

Is it ok to use reference to main.jsxbin inside manifest.xml?

[Justin Taylor-Hyper Brew]

Should be fine, I typically use a main.jsx to eval my app.jsx (which turns into app.jsxbin upon delivery), that way I can refresh changes without closing/re-opening my app.

[karpiyon · Accepted solution]

It is working now.

The installation as well.

What was wrong...

I create a few scripts, in unix, which copy the files for me.

I think it had to do with new line char which is added in one machine - not sure.

[Justin Taylor-Hyper Brew]

Darn line ending mismatches are the worst. When facing super weird behavior always check/reset permissions, verify line endings, check hidden files (dot files), wipe prefs, restart machine.

[karpiyon]

Do you have a trusted timestamp server to access for the signature?

This afternoon  -tsa http://time.certum.pl/ was working but now i get:

Error - the timestamp returned from the chosen TSA could not be verified, so the ZXP created is likely to be rejected by other tools. Please recreate your ZXP with a different trusted TSA.

[Erin F.]

Hi karpiyon​,

In the past, I've seen dome developers recommend http://timestamp.digicert.com/ and Time Stamping Server | Sectigo™ Official Site

[Justin Taylor-Hyper Brew]

I use http://timestamp.digicert.com/

[karpiyon]

I finally found the problem...

Looking at this post: Trying to make ZXP, selfsigned certificate not valid

I when over the META-INF/signatures.xml file and realized searched all the file references.

the problem was with the hidden properties of the .debug file which was copied.

After deleting this file the signature passes.

[Justin Taylor-Hyper Brew]

.debug file shouldn't prevent signing (as I've done this successfully before), however, I've seen in a lot of cases where the .debug file gets excluded at some point in the packaging/installing which will make the panel invalid upon launch since the package no longer matches when it was signed.

[karpiyon]

Yes, this is what happens.

As i mentioned in one of my replies, I tried to create the packaging process on 2 different machines.

My pre script - the one which copies all the files, merges them, rename etc runs on linux or kali.

on the kali machine it changes the attributes of the .debug and turn it to hidden.

This probably makes it invisible for the verify process.