Lines Matching refs:permissions

12         <li><a href="#runtime-permissions">Testing Permissions</a></li>
35   <li><a href="#runtime-permissions">Permissions</a>
49 <h2 id="runtime-permissions">Testing Permissions</h2>
52   The new <a href="{@docRoot}preview/features/runtime-permissions.html">Permissions</a> model
53   changes the way that permissions are allocated to your app by the user. Instead of granting all
54   permissions during the install procedure, your app must ask the user for individual permissions
57   can grant or revoke the permissions granted to an app individually at any time. This feature of
65   should begin planning your app’s migration to the new permissions model now, with a goal of
74   permissions behavior.
78   <li>Identify your app’s current permissions and the related code paths.</li>
83       <li>List permissions and status by group:
84         <pre>adb shell pm list permissions -d -g</pre>
86       <li>Grant or revoke one or more permissions using the following syntax:<br>
91   <li>Analyze your app for services that use permissions.</li>
97   The permissions change affects the structure and design of your app, as well as
99   permissions use and start planning for the new flows you want to offer. The official release of
105   Identify the permissions that your app actually needs and uses, and then find the various code
108   runtime permissions by changing the app’s {@code targetSdkVersion} to the preview version. For
114   Test with various combinations of permissions revoked and added, to highlight the user flows that
115   depend on permissions. Where a dependency is not obvious or logical you should consider
121   For more information on the behavior of runtime permissions, testing, and best practices, see the
122   <a href="{@docRoot}preview/features/runtime-permissions.html">Permissions</a> developer