On one test machine, our extension wouldn't load, because [NETransparentProxyManager loadAllFromPreferencesWithCompletionHandler]
can't find a manager, saying Skipping configuration appname because it is of the wrong type
. This is the first time I've seen this behaviour.
(The containing app tries to find a configuration, if it can't find it it creates one, then modifies whatever it found or created, then stores it. I don't have the right logging yet for that, so I can't see the error messages. [NSLog
instead of os_log_error
.])
That log entry pretty much means what it says: +[NETransparentProxyManager loadAllFromPreferencesWithCompletionHandler:]
found a configuration but it it:
- Has no VPN property, or
- The protocol type is not plug-in, or
- The tunnel type is not app proxy
It’s not clear how you managed to get the system into this state but I don’t think there’s any way to get out of it using the API (you can’t remove the configuration using the API because you can’t get a handle on it).
If the configuration comes from a configuration profile, you could simply remove the profile.
If not, check whether it shows up in System Settings and, if it does, remove it from there.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"