Merge "Docs-change: how UserManager.ENSURE_VERIFY_APPS affects profiles." into oc-dev

am: baa85250d4

Change-Id: I553b5b775cbdb42020405dfcc1b18032d4777597
This commit is contained in:
Benjamin Miller
2017-07-20 14:05:31 +00:00
committed by android-build-merger

View File

@@ -389,10 +389,13 @@ public class UserManager {
public static final String DISALLOW_ADD_MANAGED_PROFILE = "no_add_managed_profile"; public static final String DISALLOW_ADD_MANAGED_PROFILE = "no_add_managed_profile";
/** /**
* Specifies if a user is disallowed from disabling application verification. * Specifies if a user is disallowed from disabling application verification. The default
* Starting from {@link android.os.Build.VERSION_CODES#O}, application verification * value is <code>false</code>.
* is enforced across all users on the device if a profile owner or device owner sets *
* this restriction to <code>true</code>. The default value is <code>false</code>. * <p>In Android 8.0 ({@linkplain android.os.Build.VERSION_CODES#O API level 26}) and higher,
* this is a global user restriction. If a device owner or profile owner sets this restriction,
* the system enforces app verification across all users on the device. Running in earlier
* Android versions, this restriction affects only the profile that sets it.
* *
* <p>Key for user restrictions. * <p>Key for user restrictions.
* <p>Type: Boolean * <p>Type: Boolean