Fix documentation for revokeSelfPermissionsOnKill API

Killing the app right after revokeSelfPermissionsOnKill
prevents permission revocation as the IPC call is not yet
completed due to async nature.

Fix: 311557928
Test: build
Change-Id: Id54eff506825f79583ec11b85b481bffc3b2b306

1 files changed, 4 insertions, 3 deletions

diff --git a/core/java/android/content/Context.java b/core/java/android/content/Context.java
index bad73fc68f3a..4fcf6b66895c 100644
--- a/core/java/android/content/Context.java
+++ b/core/java/android/content/Context.java
@@ -7188,9 +7188,10 @@ public abstract class Context {
      * as the package remains in the foreground, or has any active manifest components (e.g. when
      * another app is accessing a content provider in the package).
      * <p>
-     * If you want to revoke the permissions right away, you could call {@code System.exit()}, but
-     * this could affect other apps that are accessing your app at the moment. For example, apps
-     * accessing a content provider in your app will all crash.
+     * If you want to revoke the permissions right away, you could call {@code System.exit()} in
+     * {@code Handler.postDelayed} with a delay to allow completion of async IPC, But
+     * {@code System.exit()} could affect other apps that are accessing your app at the moment.
+     * For example, apps accessing a content provider in your app will all crash.
      * <p>
      * Note that the settings UI shows a permission group as granted as long as at least one
      * permission in the group is granted. If you want the user to observe the revocation in the