From 716cf78bfe6505b7c0152835d243f0aee9ecf58c Mon Sep 17 00:00:00 2001
From: kholoud mohamed <kholoudm@google.com>
Date: Wed, 22 Apr 2020 16:24:33 +0100
Subject: [PATCH] Fix javadoc for
 CrossProfileApps#canRequestInteractAcrossProfiles

Remove the app being whitelisted requirement from
the javadoc.

Fixes: 154712757
Test: N/A
Change-Id: Ib476d0b19717e901d26039194d33f8c43f7e3f74
---
 core/java/android/content/pm/CrossProfileApps.java | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/core/java/android/content/pm/CrossProfileApps.java b/core/java/android/content/pm/CrossProfileApps.java
index 144a07eb4ea34..99e6d91a61ae0 100644
--- a/core/java/android/content/pm/CrossProfileApps.java
+++ b/core/java/android/content/pm/CrossProfileApps.java
@@ -279,12 +279,8 @@ public class CrossProfileApps {
      * <ul>
      * <li>{@code UserManager#getEnabledProfileIds(int)} ()} returns at least one other profile for
      * the calling user.</li>
-     * <li>The calling app has requested</li>
-     * {@code android.Manifest.permission.INTERACT_ACROSS_PROFILES} in its manifest.
-     * <li>The calling package has either been whitelisted by default by the OEM or has been
-     * explicitly whitelisted by the admin via
-     * {@link android.app.admin.DevicePolicyManager#setCrossProfilePackages(ComponentName, Set)}.
-     * </li>
+     * <li>The calling app has requested
+     * {@code android.Manifest.permission.INTERACT_ACROSS_PROFILES} in its manifest.</li>
      * </ul>
      *
      * <p>Note that in order for the user to be able to grant the consent, the requesting package