Category filter

Configuration profile to prevent app uninstallation on iOS devices

In an organizational setting, maintaining control over the applications installed on company-provided devices is crucial. It is essential for IT admins to ensure that all applications on company owned devices are securely maintained and accessible all the time. It includes preventing the uninstallation of managed apps on the devices. By using a configuration profile IT admins can prevent the app removal. With Hexnode’s Deploy Custom Configuration feature, IT admins can deploy a configuration profile to prevent app uninstallation on the iOS device.


The configuration profile provided below is adapted from a third-party open-source site.


This configuration profile is supported only on supervised devices running iOS 4.2.1 and above.

Configuration profile to prevent uninstallation of apps

The above configuration profile will prevent the user from removing the applications on the iOS device. When the ‘allowAppRemoval’ key value is set to ‘false’, users will not be able to remove the apps from the device. To allow users to remove apps from the device, set the ‘allowAppRemoval’ key value to ‘true’.

What happens at the device end?

Before applying the configuration profile, the users can uninstall the apps from the device.
Apps can be uninstalled from the device

After associating the configuration profile policy on the device, the Delete App option clicking which will uninstall the apps will be removed. The users can only remove the apps from the Home Screen, not from the device.

Option for the apps to uninstall is removed after deploying a custom profile to prevent app uninstallation on iOS


  • To create and customize configuration profiles, you can use tools like Apple Configurator, Profile Manager or manually create them using text editors.
  • Use non-encrypted .mobileconfig, .xml, or plist files to deploy profiles across devices.
  • Ensure that you do not associate conflicting configurations with the devices.
  • Use wildcards to fetch key values from the portal.
  • It is recommended to manually validate the configuration profile execution on a system before executing the action in bulk.
  • Hexnode will not be responsible for any damage/loss to the system on the behavior of the configuration profile.

  • Configuration Profile Repository