fcamarlinghi / grunt-cep Goto Github PK

Hello,
On older versions of Indesign (2017), I built my zxp on my Windows, and it worked well on both Indesign Mac and Windows.
With Indesign 2018, it doesn't :

• if I build zxp on my windows, it works on Indesign 2018 windows but not mac (white screen and do nothing) (grunt-cep 0.4.4 and 0.4.3)

• if I build it on mac, it works on Indesign 2018 mac and it seems to work on windows too ! (grunt-cep 0.4.4 because cannot build it on mac on 0.4.3 see zxp-provider last release)

Furthermore with the new version of grunt-cep, I have this problem for Indesign 2017 too :

• if I build zxp on mac, it works on Indesign 2017 in both windows and mac

• if I build it on windows, it doesn't work on Indesign 2017 windows neither mac (grunt-cep 0.4.4 but worked with grunt-cep 0.4.3)

Any idea ?

Thanks !

I'm trying to use the cep:debug task to debug my extension, but am hitting the following error, taken from: CEP8-IDSN.log

2018-10-22 14:32:30:153 : DEBUG Found extension with id 'acme.indesign.exporter.panel.debug'
2018-10-22 14:32:30:156 : DEBUG Missing DispatchInfo detected
2018-10-22 14:32:30:158 : INFO  Removing extension with id 'acme.indesign.exporter.panel.debug' because it is incomplete

Packaging the extension using cep:release and installing it results in the extension being loaded as expected.

When comparing the two manifest.xml files - one from the installed packaged extension in C:\Program Files (x86)\Common Files\Adobe\CEP\extensions\acme.indesign.exporter.panel and one from the debug-mode extension in %APPDATA%\Roaming\Adobe\CEP\extensions\acme.indesign.exporter.panel.debug - the only difference is the .debug suffix on the extension ID and the (debug) suffix on the extension name.

Any ideas what may be causing this?

Hello,
Since last Adobe Extension Manager update (22 March 2018), zxp generated by grunt-cep cannot be installed :
Installation failed because the extension does not contain a valid code signature.

I found this release note :
https://helpx.adobe.com/extension-manager/release-note/extension-manager-cc-release-notes.html

And in particular those points :

• For hybrid extensions, the MXI file must set "file-type" to "CSXS" for all embedded CEP extensions
• For hybrid extensions, Extension Manager CC only validates the signature of the outer extension. The signature of an embedded CEP extension is not validated

Any idea ?
Thanks

For CC2018 and CC2018 the familyname for Flash inside the hosts.json is set to "Animate".

An extension released with such value would fail to install with the following message:

Installation failed because the extension is not compatible with the installed applications.

Switching the familyname back to "Flash" would resolve the problem.

Hello, is it possible to debug jsx files? Or is it out of the scope of this grunt plugin?

Thanks,

Hi,
I cannot sign my zxp on my Debian 9 because of a problem on a module that you use to get ZxpSignCmd path/executable (zxp-provider).
I've opened an issue on that project too (codearoni/zxp-provider#13).

A workaround for me would be to be able to pass as a parameter the "zxp_path" that you use on your command to sign zxp. In fact, I have a ZXPSignCmd on my Debian that works well ! (Using an exe and wine command)
If I work on it to add that as a parameter ; would you accept my PR ? (I don't want to work on it for nothing 😉 )

Thanks !

Hello,
Not sure of all the hosts but following two are wrong for mac binary name.

Thanks,
Paresh

I'm trying to use the cep:debug task to debug my extension, but am hitting the following error, taken from: CEP8-IDSN.log

2018-10-22 14:32:30:153 : DEBUG Found extension with id 'acme.indesign.exporter.panel.debug'
2018-10-22 14:32:30:156 : DEBUG Missing DispatchInfo detected
2018-10-22 14:32:30:158 : INFO  Removing extension with id 'acme.indesign.exporter.panel.debug' because it is incomplete

I'm using InDesign 2018 v13.1

Packaging the extension using cep:release and installing it results in the extension being loaded as expected.

When comparing the two manifest.xml files - one from the installed packaged extension in C:\Program Files (x86)\Common Files\Adobe\CEP\extensions\acme.indesign.exporter.panel and one from the debug-mode extension in %APPDATA%\Roaming\Adobe\CEP\extensions\acme.indesign.exporter.panel.debug - the only difference is the .debug suffix on the extension ID and the (debug) suffix on the extension name.

Any ideas what may be causing this?

Expected behavior

all cef_params entries are listed as <Parameter> tags inside <CEFCommandLine> in the generated manifest.xml for all the builds

Actual behavior

only the first build contains the <Parameter> tags expected, every subsequent build has an empty <CEFCommandLine> node.

Steps to reproduce the behavior

1. configure multiple builds from the options.builds property of the configuration
2. run the cep:release command to generate the final zxp that should bundle all the builds
3. inspect the manifest files included in the zxp

The command grunt cep:package always generates the output at <project folder>/staging and ignores the staging path option given in the cep-config.js file.

That option only works with grunt cep:debug, I think it sould work with grunt cep:package too, or add another way to configure the folder for the package output.

Hello,

Could you please update the npm registry? It still serves 0.4.2 instead of 0.4.3 (important for CC2018)

https://www.npmjs.com/package/grunt-cep

Thanks

I have cep extension for the premiere and I want to be auto-update could you please guide me how to do that ?

One of our panels is set up to make builds for Prelude CC2015.5 and CC2017.
The problem we run in to is the launch profile only tries to find CC2015.5, not CC2017, so some developers have to manually switch the order around.

Is there a way to configure this that we haven't found?
If not, I can try to find some time to work on a PR for this.

I'm trying to use the cep:debug task to debug my extension, but am hitting the following error, taken from: CEP8-IDSN.log

2018-10-22 14:32:30:153 : DEBUG Found extension with id 'acme.indesign.exporter.panel.debug'
2018-10-22 14:32:30:156 : DEBUG Missing DispatchInfo detected
2018-10-22 14:32:30:158 : INFO  Removing extension with id 'acme.indesign.exporter.panel.debug' because it is incomplete

Packaging the extension using cep:release and installing it results in the extension being loaded as expected. When comparing the two manifest.xml files - one from the installed packaged extension in C:\Program Files (x86)\Common Files\Adobe\CEP\extensions and one from the debug-mode extension in %APPDATA%\Roaming\Adobe\CEP\extensions - the only difference is the .debug suffix on the extension ID and the (debug) suffix on the extension name.

Any ideas what may be causing this?

The updated apps released a few days ago have in some (all?) cases had a major version bump (Prelude is now 5.0, Photoshop is 17.0 etc.) which breaks the manifests, and the application paths have also changed at least on OS X to now have ... CC 2015.x in the file path, but not 100% consistently as shown in these examples:
Adobe Prelude CC 2015.4/Adobe Prelude CC 2015.app
Adobe Photoshop CC 2015.5/Adobe Photoshop CC 2015.5.app
... which breaks the launch profile.

For manifests, a simple fix could be to just set the minimum version rather than a range, as shown here: Adobe-CEP/CEP-Resources#60 (comment).

The other option would be to make a new family, CC2015.5?
It's hard to decide as only Photoshop and Illustrator are on CEP7, the rest are still CEP6.1 but have these changed major versions and paths.
Not sure about the best option so I'm opening as a conversation

I can't figure out how I can make grunt-cep copy a folder to the extension installation folder whenever it is changed. It is possible to do? It already does when running the cep task, but I need to update it every time it is modified without having to relaunch the host app.

When I run grunt cep:debug I get the following error:

Fatal error: Unable to find Adobe Illustrator CC2020 executable at "/Applications/Adobe Illustrator 2020/Adobe Illustrator 2020.app".

My executable is found at this path:
/Applications/Adobe Illustrator 2020/Adobe Illustrator.app

Is there a way to specify the correct path in the options?

Could you update the npm registry? It still serves 0.3.5 instead of 0.4.1:

https://www.npmjs.com/package/grunt-cep

Hi,
Can this be done?
For compatibility with grunt-init-cep

When building a package for Premiere Pro CC 2015, the MXI file created is not valid. The Adobe Exchange and the ExManCmd commandline utility will reject the created zxp because of it.

The problem is the following:

            <product familyname="Premiere" maxversion="9.9" primary="true" version="9.0" />

familyname only works for some Adobe products it seems. To make this install in Premiere, it should use the 'name' attribute. I.E. this installs:

            <product name="Premiere" maxversion="9.9" primary="true" version="9.0" />

Hello,

I search for a solution/idea to sign my CC extension on a continuous integration build environnement.

This env. is based on OS linux.

Thank you very much,

porcinet