On 3 Mar 2016, at 01:35, Kevin Yu <kevi...@draytek.com> wrote: > Any suggestion?
The most common problems I see in this space are: * code signing issues — You have to make sure that both your app and your provider extension are signed with the special Network Extension entitlements, and both are covered by a provisioning profile that whitelists those entitlements. See the following DevForums post for details. <https://forums.developer.apple.com/message/75928#75928> * 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 Share and Enjoy -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/archive%40mail-archive.com This email sent to arch...@mail-archive.com
