site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:reply-to:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=ncr1vE6+7kAsP8c5/QsluIHpCFRst5Veh/melf75hPE=; b=cUR13KVNSzhv2veItUTGQTD4TvdbMHJdIryyZyjOnyIu46SLZWF4eozdzDUIHOoj+o c0QQDlVVZcJfLStJuCSN7JmNR+aHaWjkyEohVp4NxoY5svNukBYh3v3e2ADBN5JsSgn8 nKqC0UFtYGKChP9xqD6A15h/kIICfD/KVuht9gRaHbMpJ1kEl7GmFwX6LjY3tJE3k12/ Kg9LoPlQ7LzP0uqs5Kvpp26HTK1tX7G0aV7nXwRPr0+OnT8EJ6H41d/o5Zr1/mLYVgyl hjOtsB6rN0r0mFVGLHGvCXTCc43PxdLQLGRhCM2amsmSIQ44jnYhwQd2NLGug3w93kJ8 inhA== User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 Thanks for the tip Lyndon. That didn't work either. DFT FxPlug.app/: a sealed resource is missing or invalid NO On 8/27/17 9:01 AM, Lyndon Hill wrote: Hi Paul, I had a similar experience. I don’t think I nailed down a series of steps to make it compile and work out of the box straight away. Just make sure that the target you compiled did in fact create the plugin inside the application bundle. Run the application, maybe reboot too. Then magically the problem goes away. Check the console after running Motion or run Motion from the shell to check any messages regarding the plugin. You don’t need to fiddle with pluginkit. Lyndon _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com Here is something that DID work. I created a whole other user, logged into that, ran the FxPlug .app, then ran pluginkit -m, and it showed up! Also, there were more than a page of entries in the pluginkit output. When I'm logged into my normal user, there are only maybe ten or so! So what's going on here? How do I get my normal user account to see all of the usual pluginkit entries that appear for other, new, users? Another note: I noticed that after turning on code-signing for the template plugin, the signing failed. check-signature explains that an embedded framework: In subcomponent: .../DFT FxPlug.app/Contents/PlugIns/DFT FxPlug.pluginkit/Contents/Frameworks/FxPlug.framework FxPlug.framework is malformed, at least according to the ever-changing code-signing rules in Sierra. How am I supposed to rectify this?