Quinn, Thanks a lot for the information that I did not know before. it turns out my plugin did not registered at all. Now my question became, how to registered my plugin when deploy the app to other machine? Because in iOS, it install via app store (or TestFlight) and iOS can handle it well, we did not notice any plugin register operation is needed, it just works. We also plan to deploy the developing app via Mac’s App Store, what operation is needed for going this way?
— Kevin > > >> Any suggestion? > > > * extension registration — Registration problems are more common on OS X than > iOS because the app install process is more free form. You can confirm that > the extension is registered with the following command: > > $ pluginkit -m -p com.apple.networkextension.packet-tunnel > > This should produce output that shows your extension. To get a feeling for > the output you should expect to see, you can run the command for some other > extension point. For example, to see share extensions: > > $ pluginkit -m -p com.apple.share-services > > If your extension isn't registered, you should do two things: > > - Install your app on a fresh machine (I use a VM for this, rolling back to a > snapshot for each debugging iteration) to see that it works in general. A lot > of the time problems like this only occur on your development machine, where > you're continually creating and launching new versions of the app. > > - On your development machine you can force the extension to register using: > > $ pluginkit -a /path/to/extension
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/archive%40mail-archive.com This email sent to [email protected]
