Lines Matching full:your
4 page.metaDescription=Learn about runtime permissions and how they make it easier for users to install and upgrade your apps.
56 <li>Normal permissions do not directly risk the user's privacy. If your app
62 data. If your app lists a normal permission in its manifest, the system
64 user has to explicitly give approval to your app.
75 On all versions of Android, your app needs to declare both the normal and the
78 that declaration is different depending on the system version and your
83 <li>If the device is running Android 5.1 or lower, <strong>or</strong> your app's target SDK
84 is 22 or lower: If you list a dangerous permission in your manifest, the user
89 <li>If the device is running Android 6.0 or higher, <strong>and</strong> your app's target SDK
101 API level. You should test your app to verify that it behaves properly when
102 it's missing a needed permission, regardless of what API level your app
111 simpler, since your app doesn't need to check which version of Android it's
118 If your app needs a dangerous permission, you must check whether you have
148 If your app needs a dangerous permission that was listed in the app manifest,
167 In some circumstances, you might want to help the user understand why your
205 If your app doesn't already have the permission it needs, the app must call
208 permissions. Your app passes the permissions it wants, and also
251 <strong>Note:</strong> When your app calls {@link
254 Your app <em>cannot</em> configure or alter that dialog box. If you need to
265 When your app requests permissions, the system presents a dialog box to the
266 user. When the user responds, the system invokes your app's {@link
268 onRequestPermissionsResult()} method, passing it the user response. Your app
305 group</a> your app needs access to; it does not list the specific permission.
308 system dialog box just says your app needs access to the device's contacts.
310 your app requests any other permissions in that group (that are listed in
311 your app manifest), the system automatically grants them. When you request
312 the permission, the system calls your {@link
316 same way it would if the user had explicitly granted your request through the
321 <strong>Note:</strong> Your app still needs to explicitly request every
324 change in future Android releases. Your code should not rely
332 android.Manifest.permission#WRITE_CONTACTS WRITE_CONTACTS} in your app
341 If the user denies a permission request, your app should take appropriate
342 action. For example, your app might show a dialog explaining why it could not
352 immediately denies the request. The system calls your {@link
356 same way it would if the user had explicitly rejected your request again.
