Thanks, I'll look into Profile Manager. In the meantime I went with a free 30 trial of one of the MDM providers.

Did we ever get an answer to this. I find myself in the same situation.

You are doing nothing wrong, but have probably hit a bug in Xcode dating back to Xcode 10.1 beta: " As of Xcode 10 beta 1, it seems the build settings editor GUI doesn't properly resolve the correct value for variables defined in the xcconfig files, and displays the values as if resolved with the old pre-Xcode 10 behavior. " Basically the settings really are being inherited correctly, but Xcode itself doesn't display them as if they are. This had me stumped today until I came across the above on stackoverflow /1393987/how-to-append-values-in-xcconfig-variables. To be sure, actually do a #if DEBUG .... #endif section in your code and see if the enclosed code gets called at runtime. It sure would be nice if this were fixed!

What happens if you run it from the Home screen with the USB cable connected and the Console app actually displaying that phone's logs (with and without "Include Debug Messages")? I wonder if I'm hitting an observer effect here.

I finally got around to trying Profile Manager, but whatever I did, I couldn't get it to upload the configuration plist to the device. I tested pushing other restrictions (e.g enabling and disabling the camera) and that worked, but nothing involving 'App Configuration' seems to work. My plist is pretty simple and the bundle ID is correct: xml ?xml version="1.0" encoding="UTF-8"? !DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd" plist version="1.0" dict keyManagedAppConfigurationVersion/key string1/string keyLicenseKey/key stringabcdef12345/string keyUserID/key stringwellington/string /dict /plist Watching the server's Activity Tasks view shows activity for any modification to the 'Restrictions', but setting a new 'App Configuration' doesn't create a task.

If these files are usually opened directly by the user (i.e from a Open Panel) then NSFileCoordinator might be what you want. But that is a cooperative API, i.e other processes also need to use FileCoordinator to access the file too. Give more details on your use case.

@eskimo - Any chance of listing the figures for iOS 16? Any changes?

Feedback submitted - FB15041621