Post

Replies

Boosts

Views

Activity

Reply to Ensuring own Framework continues to be loadable by other apps, which may be Hardened and/or Sandboxed
@FxFactory thanks for the feedback. There seems to be an older version of the SDK in "/Library/Developer/Frameworks/PluginManager.framework/" indeed. I have installed the latest SDK though (v4.2.4). It's weird though, that the example targets from the latest SDK still point to the old versions of the frameworks. I have tried pointing our project to the newer version which is located under /Library/Developer/SDKs/FxPlug.sdk/Library/Frameworks. However, code signing fails in that case with the following error message: "bundle format unrecognized, invalid, or unsuitable. Command CodeSign failed with a nonzero exit code". This is mentioned as a known issue in the release notes for version 4.0 in which case a manual copy/sign step via a run script phase is recommended. We did just that but the exact error persists in the manual code signing step so we're stuck :-( I also tried going the route you suggested, but unfortunately it yields the same issues, eventually.
Sep ’22