Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

  • Announcements

    • Allan

      Forum Rules   04/13/2018

      Hello folks! As some things are being fixed, we'll keep you updated. Per hour the Forum Rules don't have a dedicated "Tab", so here is the place that we have our Rules back. New Users Lounge > [READ] - InsanelyMac Forum Rules - The InsanelyMac Staff Team. 
Sign in to follow this  

iOS profiles and not specified restrictions in Payload

2 posts in this topic

Recommended Posts



As some of you probably know we have a software from Apple called 'iPhone configuration utility'. You can use it to generate iOS profiles in plist format.


One of the payloads in such profile is "Restrictions".

Apple is giving us reference about it here: http://developer.apple.com/library/ios/#featuredarticles/iPhoneConfigurationProfileRef/Introduction/Introduction.html


However I can't find out what happens if you miss some key. For instance, if in my plist file, under Restrictions payload there will be no "allowCamera" key (which should be set to either true or false), what will happen? Will camera be available or not? Some keys have their default values (as reference shows) but some of them don't?


This issue came to our mind when Apple release new restrictions key and we won't update our profile, what is going to happen with restrictions which keys weren't specified in the plist profile.





Share this post

Link to post
Share on other sites

In my understanding if all Restrictions are "Optional" and documentation explains what happens IF set to false, does it mean that they are all true by default? (except one restriction `forceITunesStorePasswordEntry` where it explains what happens if set to true, which means that it's false by default?)


I guess that if restriction is not specified in configuration profile then it shouldn't make any changed to `brand new` iOS (that would make sense).


Correct me if I'm wrong.


Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.