New Signing Requirement for AE and PR extensions as of 25.2.0

Question

It appears that a recent AE update changed requirements for plugins to be run  while this is a marginal win for anti-piracy (it requires pirates to self sign their bundles, or write an installer to do so, but let's face it most pirates are not buying luxury computers), it would mostly seem to break older plugins which for various reasons have decided not to sign. Since most of the effected plugins are free (The best reason not to sign a bundle is because it costs $99 a year) there are probably a few useful and widely used plugins that have been bricked. Is there a place this change could be documented? is there a place the error codes in the plugin loading logs are documented?

Richard Rosenman · Answer

Yeah, I wrote a thread about this too: https://community.adobe.com/t5/after-effects-discussions/notarizing-and-signing-mac-plugins-for-release-sdk/m-p/15063711#M259878

I dropped Mac support due to this. Apple is becoming an increasingly closed off system and they've taken all the fun out of plug-in development by having to notarize, certify and what-not, as well as dish out an annual fee.

I'm sure there are other developers like me that will feel it's simply not worth their while to jump through hoops to create an app for Mac.

-Richard

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded