This page explains how to request the user’s permission for your application to access data on the device or use a device feature such as a built-in camera or microphone.
Google’s guideline for requesting permissions recommends that, if the user denies a permission request once, you should display the reason for the request and present the request again.
For more information on when and how to request permissions on an Android device, refer to App permissions best practices in the Android developer guide.
The runtime permissions API requires Android version 6 (API level 23). To change your application’s target API:
Before the application requests permission to use restricted data or a particular device feature, it must declare the permission in its Android App Manifest. For more information, refer to Declare permissions for an application.
The Android.Permission API provides functionality that you can use to check what permissions the application currently has and request permissions that the application requires but doesn’t have.
An overview of the process to request permission at runtime is as follows:
Use Permission.HasUserAuthorizedPermission to check if the user has already granted permission for the data or feature the application requires.
For a code example that shows how to use this API, refer to Permission.HasUserAuthorizedPermission.
Use Permission.ShouldShowRequestPermissionRationale to check whether you need to display the rationale for a specific permission request.
If the rationale is necessary, display a message with reason why your application requires access to specific device features. After you display the message, send a request for permission.
If the rationale isn’t necessary, directly proceed to send a request for permission.
For a code example that shows how to use this API, refer to Permission.ShouldShowRequestPermissionRationale.
Use Permission.RequestUserPermission to request permission to use the data or feature. When you call this method, Android opens the system permission dialog that the user can use to grant or deny the permission.
For a code example that shows how to use this API, refer to Permission.RequestUserPermission.
Use Permission.RequestUserPermissions to request permissions to access multiple resources on the user’s device at once. This method uses an array of strings with each string representing a specific permission to access a particular resource such as the device’s camera , microphone, or location.
These methods can accept a PermissionCallbacks object that you can use to specify code to run after the user grants or denies the permission. You can use this to start using a device feature as soon as the user grants the permission request. For example, you can start recording from the microphone.
Tip: When you request permission, it’s best practice to show the user a message that explains why the application requires the feature.
Note: If the user has enabled the Do not ask me again option on the system permission dialog, or has denied the permission more than once, RequestUserPermission()
doesn’t open the system dialog. In this case, the user must go into the application permission settings and manually enable the permission.
If the user denies the permission that the application requires, provide a way for the user to manually display the permission request dialog. How to do this depends on the application, but one solution is to provide a button that calls Permission.RequestUserPermission.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
More information
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising. Some 3rd party video providers do not allow video views without targeting cookies. If you are experiencing difficulty viewing a video, you will need to set your cookie preferences for targeting to yes if you wish to view videos from these providers. Unity does not control this.
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.