On 10/23/2014 3:18 PM, Darrin Cardani wrote: We updated the documentation with FxPlug 3.0.1 (the recent release) to show a more efficient way to do this. That said, Plug-ins built the old way should continue to work. They don't seem to be. A heads-up for everyone else out there with FxPlug3 bundles. _______________________________________________ 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 If existing plug-ins aren’t working, check the console.app logs to see if it says why. Usually PlugInKit or the host app will say something about not being able to load it. You do need to ensure that the protocol listed in the XPC’s Info.plist file matches the one you’re using (or is NSObject if you don’t need a protocol because your XPC doesn’t actually do anything). I did check the console and it was complaining about something related to the protocol. I've just finished converting the bundles over to the newer way so I can't tell you what the error was.