importAEComps returning true but silently failing to import compositions in Premiere

Premiere Pro
1

I’m running into a silent failure where both importAllAEComps and importAEComps return true immediately, but no compositions are actually imported into the Premiere Pro Project Panel.

Here is the exact code I am running:

const importPath = "/Users/Shared/WolfgangTemp/1.aep";
const compNames = \["Hero", "Villain", "Pot", "Board", "Game Info"\];

Both of these return true, but nothing appears in the project panel:

const successAll = await activeProject.importAllAEComps(importPath);
const successSpec = await activeProject.importAEComps(importPath, compNames);

What I’ve verified:

  1. Manual drag-and-drop of the same 1.aep file into Premiere works perfectly. The compositions exist and are healthy.
  2. File permissions have been ruled out. I’ve copied the .aep locally to /Users/Shared/ to bypass macOS TCC sandbox restrictions, but it still fails. I’ve also tried local temp folders, direct project directories, and other path variations.
  3. Checked that dynamiclinkmanager and aerendercore processes are active in memory.
  4. Polled the project items for up to 90 seconds, but the compositions never register.

Is this a known regression in Premiere Pro v26’s UXP DOM, or is there a specific path format/manifest setting required to make the Dynamic Link script bridge work?

Thanks!

[1]
Environment:

  • OS: macOS 27 Golden Gate Beta (M3 Ultra)
  • Premiere Pro Version: v26.2.2 (latest)
  • After Effects Version: v26.2.1 (latest)
  • API: UXP JavaScript DOM

  1. Footnotes ↩︎

2

Hi @mits,

Can you try specifying a target bin for the comps to be imported into? For example importing into the root bin via:

const rootItem = await activeProject.getRootItem();
const rootBin = ppro.ProjectItem.cast(rootItem);

const successAll = await activeProject.importAllAEComps(importPath, rootFolder);
const successSpec = await activeProject.importAEComps(importPath, compNames, rootBin);

or whichever bin of your choice and see if that helps?

1 Like
3

oh wow, I assumed not specifying a target would automatically aim it at the root bin. This worked! thank you!