- Edited
iOS - Orion
When a .mobileconfig file is downloaded via Safari, it automatically downloads the profile to the device to be installed/activated via settings. In contrast. when a .mobileconfig file is downloaded in Orion, it just downloads the file to my Files on my device, which cannot be downloaded to the device from there.
This is not a very common action, but during some server software development I'd find myself deleting and redownloading profiles fairly often. Additionally this would prevent the need for a user to offload work to Safari or leaving them confused why their profile download is not working from Orion.
A workflow for a normal user would be setting up a .mobileconfig profile from NextDNS:
- On iOS, log in to https://my.nextdns.io
- Configure a profile (for testing purposes)
- Attempt to set up the .mobileconfig via https://apple.nextdns.io (see instructions on that page)
- Go through the process and press "Download" when complete
You'll notice that with Orion, the file downlaods to Files. With Safari, it downloads the profile to then be enabled by the user in Settings. The current workaround is to generate a URL from this page and open it in Safari to download the profile.
When Safari handles .mobileconfig profiles, the user is prompted with "This website is trying to download a configuration profile. Do you want to allow this?" and a "Ignore" or "Allow". When "Allow" is selected, it downloads the profile to the device which can be enabled in Settings by the user later.
When "Allow" is pressed another prompt appears indicating the profile has been downloaded. This prompt might be an implementation detail of iOS but I am unsure.
Ideally the flow in Orion would just mirror Safari