Re: packet-tunnel-provider on OSX platform
Re: packet-tunnel-provider on OSX platform
- Subject: Re: packet-tunnel-provider on OSX platform
- From: Kevin Brock <email@hidden>
- Date: Tue, 19 Apr 2016 22:03:22 -0700
Is the app also sandboxed? Both the app and the extension need to be sandboxed, and the entitlements should match.
Kevin
> On Apr 19, 2016, at 20:29, Kevin Yu <email@hidden> wrote:
>
>>> $ pluginkit -a /path/to/extension
>
> I use the above command to add my plugin, I can see the plugin registered via the following command
>
> $ pluginkit -m -p com.apple.networkextension.packet-tunnel
> com.draytek.SmartVPN.drayTunnelX(1.0)
> com.apple.NetworkExtension.IKEv2Provider(1.0)
>
> However, I still can not connect my plugin code.
> When I checked the console log, it shows bunch of messages like this:
>
> 2016/4/20 AM10:49:29.082 pkd[610]: ignoring mis-configured plug-in at /Users/kevinyu/Library/Developer/Xcode/DerivedData/Smart_VPN-ahmwawingpuachhkpmczcmidvxsy/Build/Products/Debug/drayTunnelX.appex: plug-ins must be sandboxed
>
> And I already checked sandbox switch for my extension and clicked “Outgoing Connections (Client)” option.
>
> Any suggestions?
>
> p.s. I did not use a fresh Machine, I use the force method to register extension, is it needed for a fresh Machine?
>
> — Kevin
>
>
>
>
>> email@hidden 於 2016年3月5日 上午4:00 寫道：
>>
>> 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
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Macnetworkprog mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden