Grant permissions on phone
Stay organized with collections
Save and categorize content based on your preferences.
When users try to open your app and lack necessary permissions, use the Message
template to tell them they need to grant permissions.
In Android Auto, if you have used the method described in
Request Permissions,
the permissions dialog will open on the phone, as long as the user is not
driving (for technical details, visit
Handle user input).
In this case, provide a toast directing the user to the phone. Then, after
permissions are granted, refresh the car screen so the user doesn't return to
the Message template.
First, the app requests permissions on the car screen...
...and then the user confirms permissions on their phone when not
driving.
Sample flow
| User action |
Where action is performed |
Step count after action |
| The user opens the app. |
On your landing template (not shown) |
1 |
| The user selects the option to grant app permissions, then reviews the
confirmation toast. |
First, use the Message template with two buttons to allow users the
chance to grant the permissions that they need:
Then, display a toast on that same Message template to direct the user
to their phone:
|
2 |
| The user grants permission on their phone.
|
No template, as this action occurs on the user's phone:
|
2 (no interaction with app in car) |
| After the user grants permissions, the app returns to the landing
template. |
Landing template; in this case, the Place List (navigation) template:
|
1 (step count resets) |
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-07-23 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-07-23 UTC."],[[["\u003cp\u003eWhen users lack necessary permissions, use the Message template to inform them and provide an option to grant permissions.\u003c/p\u003e\n"],["\u003cp\u003eIn Android Auto, the permission dialog opens on the user's phone when they are not driving, requiring a toast to direct them.\u003c/p\u003e\n"],["\u003cp\u003eAfter permissions are granted, refresh the car screen to transition from the Message template to the intended content, such as the landing template.\u003c/p\u003e\n"],["\u003cp\u003eThe app's flow involves requesting permissions on the car screen, user confirmation on their phone, and returning to the app's landing template.\u003c/p\u003e\n"]]],[],null,["# Grant permissions on phone\n\n\u003cbr /\u003e\n\nWhen users try to open your app and lack necessary permissions, use the Message\ntemplate to tell them they need to grant permissions.\n\nIn Android Auto, if you have used the method described in\n[Request Permissions](https://developer.android.com/training/cars/apps#permissions),\nthe permissions dialog will open on the phone, as long as the user is not\ndriving (for technical details, visit\n[Handle user input](https://developer.android.com/training/cars/apps#handle-user-input)).\nIn this case, provide a toast directing the user to the phone. Then, after\npermissions are granted, refresh the car screen so the user doesn't return to\nthe Message template. \nFirst, the app requests permissions on the car screen... \n...and then the user confirms permissions on their phone when not\ndriving.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nSample flow\n-----------\n\n| User action | Where action is performed | Step count after action |\n|--------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|\n| The user opens the app. | On your landing template (not shown) | 1 |\n| The user selects the option to grant app permissions, then reviews the confirmation toast. | First, use the Message template with two buttons to allow users the chance to grant the permissions that they need: Then, display a toast on that same Message template to direct the user to their phone: | 2 |\n| The user grants permission on their phone. | No template, as this action occurs on the user's phone: | 2 (no interaction with app in car) |\n| After the user grants permissions, the app returns to the landing template. | Landing template; in this case, the Place List (navigation) template: | 1 (step count resets) |"]]