-
Notifications
You must be signed in to change notification settings - Fork 206
v0.7.0 connect failed #209
Comments
Hi @plkgq, Looking at the exception it seems to me that you are trying to store As for cocoapods, thanx for suggestion, although I think it would be better to define additional subspec so at the end we would have one for extension, and one for client app. I'll fix it when I have enough spare time. |
Ahhh... I see what's wrong. In 0.7.0 version delegate's API has changed, in func openVPNAdapter(
_ openVPNAdapter: OpenVPNAdapter,
configureTunnelWithNetworkSettings networkSettings: NEPacketTunnelNetworkSettings?,
completionHandler: @escaping (Error?) -> Void
) {
networkSettings?.dnsSettings?.matchDomains = [""]
setTunnelNetworkSettings(networkSettings, completionHandler: completionHandler)
} |
Hello, Mr. Author, first of all thank you very much for the open plugin you provided,
![WX20210622-164520@2x](https://user-images.githubusercontent.com/11607068/122897388-8b376180-d37c-11eb-871f-8ecbe662b5ce.png)
However, some problems occurred in the project upgrade recently (from 0.5.1 to 0.7.0)
The following is the problem I have on my iOS device
In the oc version, NEPacketTunnelFlow has already followed the OpenVPNAdapterPacketFlow protocol, but errors still occur. I guess there should be some problems in the type conversion, but I don’t know how to solve it.
In the swift version, there are some different problems
![WX20210622-164806@2x](https://user-images.githubusercontent.com/11607068/122897491-a30ee580-d37c-11eb-942a-91f9130635e6.png)
In addition, I found that you use APPLICATION_EXTENSION_API_ONLY in your pod project, which makes it compatible with other projects. I need to manually remove it after each install. If APPLICATION_EXTENSION_API_ONLY is not necessary, I suggest removing it. This It will be better compatible with pod projects
![WX20210622-165809@2x](https://user-images.githubusercontent.com/11607068/122897565-b457f200-d37c-11eb-8009-96243f3b586a.png)
Looking forward to your reply
The text was updated successfully, but these errors were encountered: