I pushed a configuration to my iPhone through MDM to run the content filter. However, when I modify the configuration by adding some vendor-configuration , I lose connection to the debugger and can no longer see logs or the updated configuration in Xcode. I have to build the app again. Could this be an issue with Xcode, or is it related to MDM or the configuration itself?
I think this is an unwanted consequence of two separate things:
-
Modern versions of Xcode use the network for interacting with the device.
-
When you save an NE content filter configuration, the system tears all network connections so that the filter can see them [1].
There’s a long-standing request from developers for a way to control that second behaviour (FB13516440), but that’s not happened yet.
In the absence of that, I don’t see a great way around this problem. It would absolutely make sense for you to file a bug about this issue. If you do that, please post your bug number, just for the record.
If you’re doing this a lot it might make sense for you to build some infrastructure to simplify your debugging flow. You could, for example, have the filter read its configuration from a shared app group, and then use another app to set that. That would avoid the need for a change to the vendor configuration setup, and hence this issue.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
[1] Well, not the original connections, but the new connections that apps start after their original connections tear.
