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

Non-notarized plugins not loading

Community Beginner ,
Apr 03, 2025 Apr 03, 2025
  • ISSUE
    • Version 25.2 of Premiere Pro no longer allows for non-notarized plugins
    • Version 25.1 supported this
  • STEPS TO REPRODUCE
    • Create unsigned *.plugin bundle
    • Install bundle to $mediacoreplug-ins
    • Restart Premiere, clearing the plugin cache
  • ACTUAL RESULT
    • Unable to use plugin
    • View Plugin Loading.log and see "The library could not be loaded, so the plugin is set to Ignore. The error code: 2685337601"
  • EXPECTED RESULT (in 25.1)
    • Able to use plugin, plugin loaded successfully
  • VERSION
    • 25.2.0 (build 147)
  • OPERATING SYSTEM
    • MacOS Sequoia 15.3.2

 

Running the same steps with a notarized plugin succeeds on both versions.

Bug Needs More Info
TOPICS
Effects , Interoperability or 3rd party tools
167
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

correct answers 1 Pinned Reply

Adobe Employee , Apr 04, 2025 Apr 04, 2025

Hi @reliable_Moon0876 - Is this a plugin you have developed or a third party plugin?

cc @Bruce Bullis 

Status Needs More Info
Translate
7 Comments
Adobe Employee ,
Apr 04, 2025 Apr 04, 2025

Hi @reliable_Moon0876 - Is this a plugin you have developed or a third party plugin?

cc @Bruce Bullis 

Status Needs More Info
Translate
Report
Community Beginner ,
Apr 04, 2025 Apr 04, 2025

@jamieclarke This is a plugin I'm developing

Translate
Report
Adobe Employee ,
Apr 04, 2025 Apr 04, 2025

If you build the SDK samples, do they load correctly, on that same system? 

Translate
Report
Community Beginner ,
Apr 04, 2025 Apr 04, 2025

@Bruce Bullis The SDK Sample is imported successfully, so it seems my initial assumption was incorrect about the notarization.

The plugin I'm developing is using a different build system than Xcode.  Would there be another reason why the plugin can load in the prior version and not the current one?


Translate
Report
Adobe Employee ,
Apr 04, 2025 Apr 04, 2025

Sorry, our team has zero experience with build environments, other than the supported, recommended build environment. 🙂

Confirming: The same built (non-notarized) plugin does load in 25.1, but does not load in 25.2? If so, please send me the plugin.

Translate
Report
Community Beginner ,
Apr 07, 2025 Apr 07, 2025

Hi @Bruce Bullis

 

I'm also seeing this, where a development build (built locally on my machine, not signed or notarised) works fine in 25.1 and fails to load in 25.2 on macOS 15.3.2. The same source code works fine on Windows in 25.2.

 

The structure of the bundle is reasonably simple:

foo.plugin

 \ Contents

    - Info.plist

    \ MacOS

        - foo
    \ Frameworks

        - bar.dylib

 

Both foo and bar.dylib are fat (arm64 + x86_64).

 

The plugin loading log shows

"Loading /Library/Application Support/Adobe/Common/Plug-ins/7.0/MediaCore/foo.plugin
The registry tells us not to cache so the plugin will be loaded from disk.
Loading from disk...
The library could not be loaded, so the plugin is set to Ignore. The error code: 2685337601"

Translate
Report
Community Beginner ,
Apr 07, 2025 Apr 07, 2025
LATEST

Can't seem to edit my post, but I've found a possible fix for me at least.

Seems like 25.1 would allow loading unsigned plugins, whereas 25.2 needs them to be signed.

Copying the signing step from the Xcode build for the samples has allowed the plugin to load.

codesign --force --sign - --generate-entitlement-der build/install/bin/foo.plugin --deep
Translate
Report