Install configuration profile (mobileconfig) using SFSafariViewController - Change in iOS 11.3?

I've created a native iOS application that installs configuration profiles (.mobileconfig files) on our company iOS devices. The app is required as our MDM system does not support that particular profile installation. Since iOS 11.3 it is possible to install the configuraiton profile using a SFSafariViewController by opening a URI that contains a .mobileconfig file. The user is prompted with "This website is trying to open Settings to show you a configuraiton profile". After accepting it, the configuraiton profile is displayed. Prior to iOS 11.3 opening a URI that pointed to a .mobileconfig file resulted in an empty page being displayed (I've tested with iOS 11.2.6).


Unfortunately I didn't find any information in the release notes of iOS 11.3 why it has not been possible to install a configuration profile using SFSafariViewController prior to iOS 11.3. Does anyone have more information related to this change?

Resurrecting this to see if there's any documentation or working attempts at all for this. So far, the only in-app profile installation we've seen is the old "host a local server" to send ourselves a `x-apple-aspen-config` configured header to keep the controller happy.


Nothing outside of Safari has succesfully opened any URL we've tried to receive profiles. I am *certain* there existed at least one version where pointing a SFSafariViewController at a .mobileconfig file worked, but now I am completely unable to find documentation or working code.


Anyone at all have information on this?

Help

I too am looking for a solution to essentially the same problem of configuring a user account programmatically. I really can't fathom why Apple is making this so hard. Didn't it used to be as simple as editing some .plists and putting some entries in the key store? The 'solutions' I've found so far include using an Apple-mediated 'enterprise' solution (which is not appropriate), sending an email, or downloading a file from a web page! The last two require user actions, which is precisely what a series of defaults writes, or profiles -I or equivalent APIs sought to avoid. What is this 1995? Perhaps someone can point me to a more recent discussion of this matter if I don't find it or a solution first...

Please delete this and the 'abc' comment. The web app ate the first reply after I was deemed to be "Unauthorized", but then apparently not and just did a test with the 'abc' after the initial reply was trashed!?

Install configuration profile (mobileconfig) using SFSafariViewController - Change in iOS 11.3?
 
 
Q