Lines Matching refs:permissions

2 page.tags=permissions
77   If you use permissions:
120   version of Android, the user has to grant every one of the app's permissions
123   minimize the number of permissions your app needs.
137   grant your app its permissions while they are running the app. If you
138   confront the user with a lot of requests for permissions at once, you may
140   for permissions as you need them.
144   In some cases, one or more permissions might be absolutely essential to your
145   app. It might make sense to ask for all of those permissions as soon as the
158   essential permissions at the end of the tutorial sequence.
164   The permissions dialog shown by the system when you call
168   explain to the user why your app wants the permissions before calling
186   does this, it can explain what permissions are needed. For example, the
193   request permissions during the app's normal operation.
200   permissions at run time, instead of doing so when they install the app. As a
203   all, it has all the permissions it declares in the app manifest. Under the
204   new permissions model, you can no longer make that assumption.
208   The following tips will help you identify permissions-related code problems
213   <li>Identify your app’s current permissions and the related code paths.
219   <li>Test with various combinations of granted or revoked permissions. For
223   in its manifest. You should test the app with each of these permissions
226   turn permissions on or off for <em>any</em> app, even an app that targets API
231   permissions from the command line:
233       <li>List permissions and status by group:
235         <pre class="no-pretty-print">$ adb shell pm list permissions -d -g</pre>
238       <li>Grant or revoke one or more permissions:
245   <li>Analyze your app for services that use permissions.