Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit c7cae60a authored by Eugene Susla's avatar Eugene Susla
Browse files

Deprecate docs for auto revoke manifest and Intent APIs 

Test: presubmit
Bug: 153607914
Change-Id: I9c8d0aa1432ca00b729f19749e751cb117374b0a
parent 83e9ba45

core/java/android/content/Intent.java

+3 −0
Original line number Diff line number Diff line
@@ -1884,6 +1884,9 @@ public class Intent implements Parcelable, Cloneable { 


    /**

     * Activity action: Launch UI to manage auto-revoke state.

     *

     * This is equivalent to Intent#ACTION_APPLICATION_DETAILS_SETTINGS

     *

     * <p>

     * Input: {@link Intent#setData data} should be a {@code package}-scheme {@link Uri} with

     * a package name, whose auto-revoke state will be reviewed (mandatory).

core/res/res/values/attrs_manifest.xml

+4 −21
Original line number Diff line number Diff line
@@ -1830,30 +1830,13 @@ 
        <!-- @hide no longer used, kept to preserve padding -->

        <attr name="allowAutoRevokePermissionsExemption" format="boolean" />



        <!-- Declare the app's tolerance to having its permissions automatically revoked when unused for an extended

             period of time -->

        <!-- No longer used. Declaring this does nothing -->

        <attr name="autoRevokePermissions">

            <!-- App supports re-requesting its permissions if revoked.

                 Revoking app's permissions doesn't cause user experience issues, aside from a repeated permission request.



                 Permissions may be automatically revoked from an app if unused. The app must check and possibly request the

                 necessary permission on each permission-gated call-->

            <!-- No longer used -->

            <enum name="allowed" value="0" />

            <!-- App may experience degraded functionality when its previously-granted permissions are revoked.

                 Revoking app's permissions may cause user experience issues, that are not critical to the user.



                 Apps with this declaration can choose to request an exemption from auto revoke from user by starting

                 an activity with {@code Intent.ACTION_AUTO_REVOKE_PERMISSIONS}. -->

            <!-- No longer used -->

            <enum name="discouraged" value="1" />

            <!-- User may experience severe consequences if this app's permissions are revoked unexpectedly.



                 E.g. app may fail to do a user-critical background job that may likely impact user's

                 safety/security/device accessibility.



                 This declaration may cause an additional review when publishing your app.



                 Apps with this declaration are exempt from auto revoke by default, though the user has the final say

                 in both revoking the permissions as well as the app's auto revoke exemption status. -->

            <!-- No longer used -->

            <enum name="disallowed" value="2" />

        </attr>

    </declare-styleable>