No, it's still the original issue.
I'm customizing a custom vpn protocol(Wireguard) app, and trying to distribute it under Developmer ID. sample config for a connection looks like this:
Code Block | """ |
| [Interface] |
| PrivateKey = KDTZM/UpefTAosZmr75D4efcRrBYmbhSFguBye+692s= |
| Address = 10.19.49.15/24, fd9d:bc11:4021::f/48 |
| DNS = 172.26.246.127, fd4d:5a50:c7b:ed79:dbf6:bd7b:ca:f67f |
|
| [Peer] |
| PublicKey = wabNFqEBREl8rfHzJiYKqu+PZ54cwYEz0OiJZCZLwX8= |
| PresharedKey = URrUUCS6Cg6TsgPTZmcYw5pyPpsIxJLnQ9+O9waZliE= |
| AllowedIPs = 0.0.0.0/0, ::/0 |
| Endpoint = 66.42.59.203:51820 |
| """ |
Both config and info about extension path are stored inside passwordReference:
Code Block | NETunnelProviderManager.protocolConfiguration.passwordReference |
| = SecAccessCreate([ |
| kSecAttrAccess: SecAccessCreate(extensionPath, mainPath), |
| kSecValueData: config |
| ] |
| ) |
(it's not the real code, just the basic structure)
That's how tunnel connection gets created. I had to change this code, as system extension location is different from an app one. Also as system NE min deployment target is 10.15, these warnings appeared and that's why I think it may be a problem.
I'd inspected all articles I've found about this issue and I think I'd updated all the needed entitlements, that's why I'm looking in other directions.
Is there any sample app with a working system NE example? I haven't found one