EvalScript error on Premiere Pro 14.0.2

[Andaleeb Roomy]

On our CEP panel, any script run with window.__adobe_cep__.evalScript() is giving "EvalScript error." after Premiere Pro was auto-upgraded to 14.0.2. After many hours of investigation, when we downgraded to 14.0.1, it started to work again. Is this a known issue?

[Andaleeb Roomy]

Any clue about this anyone? 

[валентинн56872111]

I have the same problem on the Premiere 14.0.3. csInterface.evalScript returned "EvalScript error". After I downgraded to 14.0.1, plugin started work again.

[Bruce Bullis · Accepted solution]

As mentioned elsewhere, 14.0.2 defaults New World scripting to ON.

#include directives don't work in New World. Instead, you can follow the usage in the PProPanel sample (see /PProPanel/PProPanel.jsx); upon panel launch, it evaluates (opens) all .jsx files used within the panel.

[Andaleeb Roomy]

Hi Bruce!

Thanks for the reply. We are indeed using #include for importing json2.min.js since JSON is not available by default in ExtendScript. Didn't know about New World. Will change to evalFile now to load json2.min.js at runtime on initialization with absolute path.

Thanks,

Andaleeb

[JuniorRamos29]

Hi @Bruce Bullis,.
I'm working on a panel to run in both After Effects and PremierePro.
When I run the extension on Mac, the extension works in both AEFT and PPRO.

But on Windows, I'm getting this "EvalScript error".
And I'm having this issue with the panel on Windows just with PPRO. With AEFT runs normally.

Until try to run on Windows I wasn't aware that Premiere doesn't work anymore with the #include directive, because I'm using the //@include (and even using #include directive), still running on Mac.

So, what would be the best approach since the AEFT panel side seems not to work when I remove the include directives?