Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

CEP extension doesn't open or is blank

Explorer ,
Feb 02, 2021 Feb 02, 2021

I have a CEP extension that works on my computer perfectly fine. It is available on Exchange so it passed the review/vetting process. Some of my customers however complain that they need to uninstall it and install again every time before they open Premiere Pro (the extension is a Premiere Pro panel).

 

Otherwise they cannot open the extension panel i.e. they see it in the Window -> Extensions menu but clicking on it does nothing. Or sometimes the panel opens but it's completely blank.

 

I cannot reproduce any of that on my computer so is there a reason why it might happen and how to go about debugging it (on a customer's computer)?

 

It happens on macOS and Premiere Pro 14.8 for sure.

TOPICS
CEP , Developers , SDKs
2.0K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Sep 15, 2021 Sep 15, 2021

Hi.
I have the same problem with the latest versions of After Effects and Premiere. On Mac I can run the extensions, but on Windows they are in the menu list but won't open. Even an extension that I had already tested on Windows some weeks ago.

 

Did you find any solution to this?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Oct 15, 2021 Oct 15, 2021

When I've seen blank panels in other products, sometimes it's a manifest product number mismatch...

 

I appreciate the difficulty of not being able to test on an OS you're not running. @Kamil Pekala can you share a link to your Exchange listing, so I can check it out?

 

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 20, 2021 Oct 20, 2021
LATEST

After some time I figured out that for me the problem was related to the transition between the "old" and "new" world for adobe applications. Premiere seems has to been set the new world by default.And also seems that JSON functionalities (such as parse and stringify) work normally on Mac (at least on AE).

But on Windows, a specific JSON implementation is needed to come to work.
There are some post related to these topics at the forum.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines