Post

Replies

Boosts

Views

Activity

Reply to Ensuring own Framework continues to be loadable by other apps, which may be Hardened and/or Sandboxed
As a follow up, looks like in my case the problem is related to entitlement: com.apple.security.get-task-allow.As soon as it is stripped by a codesign it no longer works in Motion/FCPX.Same happens if I change the build settings to disable "Code Signing Inject Base Entitlements".From what I'm reading this entitlement is used for debugging, but is it in some way needed by Motion/FCPX to comunicate with the pluginkit? If so, then it means that the plugin cannot be notarized.
Mar ’20
Reply to Ensuring own Framework continues to be loadable by other apps, which may be Hardened and/or Sandboxed
I agree with everything you mentioned. But, when you download FxPlug 4 - the examples have "Code Signing Inject Base Entitlements" enabled by default (I'm trying FxSimpleColorCorrector), and just by disabling "Code Signing Inject Base Entitlements" the filters no longer work. Filters are not visible by Motion/FCPX. This one build setting change, nothing else, make the filters disappear. Everything else is straight from the FxPlug 4 SDK.I verified that with "codesign -d --entitlements :- *.pluginkit" command - as long as com.apple.security.get-task-allow entitlement exists Motion sees the filter. Once it's stripped, filter disappears in Motion.Not sure what I'm doing wrong.
Mar ’20