Understand Driver permissions
Driver App can ask the operating system for access needed by location and notification features. Each prompt, capability, platform result, local gate, and Settings page is separate. A prompt that disappears, an enabled-looking switch, returned navigation, or an available feature does not prove that every required permission is effective.
:::warning Permission choices change device state
An operating-system prompt or Settings choice can persist beyond the current Driver App screen. Respond only when you understand the capability being requested. Do not grant, deny, or change permissions merely to test a guide.
:::
Availability
Permission surfaces can appear during startup, after sign-in, when opening Map view, or when a delivery feature needs a device capability. The exact prompt and choices depend on the operating system, version, installed build, project configuration, provider state, and prior choices.
Driver App has distinct location and notification paths:
| Permission family | Current-source use | Important boundary |
|---|---|---|
| Location | Guards maps and location-dependent delivery behavior; can support foreground/background position work | Permission does not prove a fresh position, tracking, sharing, or server acceptance |
| Notifications | Allows the notification provider/OS to present alerts when available | Permission does not prove token registration, push delivery, order assignment, or alert presentation |
| iOS persistent banner style | Checks whether notification banners are temporary and can offer Later or Go to settings | Banner style is not notification permission and is not location permission |
Before you start
- Confirm that the prompt or explanation belongs to the current Driver App.
- Identify whether it concerns location, notifications, or only iOS banner presentation.
- Read the operating-system choices and your operator's privacy/work guidance.
- If a request is already unresolved, wait for the visible result instead of opening the prompt or Settings again.
Complete the task
- Read the current permission message before selecting anything.
- Match the message to the location, notification, or banner-style family.
- Choose the operating-system option that matches your intended use and the approved policy for your Driver account.
- If Driver App shows Go to settings and you intend to review a previous choice, select it once. Device Settings—not Driver App—owns the next screen.
- Return to Driver App once and wait for it to recheck the current state.
- Follow the surface now shown. A map, order, or signed-in screen is only the next local navigation state.
Lifecycle rechecks are not guaranteed to run exactly once. Avoid repeatedly leaving and returning to the app to test a permission result.
On iOS, Go to settings in an Enable persistent notifications alert is about banner presentation. It does not replace the OS notification-permission choice or any location permission.
Verify the result
Interpret the result as a sequence:
| Observable result | What it establishes | What remains separate |
|---|---|---|
| OS prompt appears | A permission was requested | Choice, effective result, App gate, and feature behavior |
| Prompt closes | The OS prompt ended | Which result was stored and whether Driver App rechecked it |
| Driver App returns to the foreground | App lifecycle changed | Permission result, provider setup, and feature readiness |
| Permission explanation remains | The current local gate still does not admit the guarded surface | Exact denied/blocked/unavailable cause |
| Guarded surface appears | A Driver App gate advanced | Complete permission coverage, GPS, push, tracking, or backend effect |
| Persistent-banner alert no longer appears | The banner check did not show the same alert in that moment | Notification permission or durable banner configuration |
States and variations
| State | Safe interpretation |
|---|---|
| Declared | The inspected native package source names a capability; no request or grant is proved |
| Requested | Driver App asked the OS/provider for a result; response is unresolved |
| Granted | One OS permission result is granted; other permissions and feature effects remain separate |
| Denied | The current result is denied; it may or may not be requestable again |
| Blocked or unavailable | The OS/build/device does not expose a normal request result for that capability |
| Local gate passed | Driver App advanced local state; it is not completeness proof |
| Settings opened | An external OS page opened; no value change is proved |
Current source selects iOS when-in-use and always-location families. Android 11 or newer selects precise, approximate, and physical-activity families. Earlier Android versions select a different source set.
For Android 10 specifically, the inspected logic compares a system-version
string to the number 10. The intended combined Android 10 request set is
therefore not established. Do not infer that all expected Android 10 location,
background, or activity permissions were requested or granted.
The source also has two local location gates. One checks returned values, while another can advance without waiting for every individual request result. Driver App documentation therefore does not certify permission completeness for any platform/build.
Troubleshooting
Driver App keeps showing the location-permission explanation
Review Understand location permissions. Do not repeat a delivery or map action to test access. If the OS control is absent or the state does not settle, contact the operator that provides the released app.
Notifications are allowed but no alert arrives
Permission is only one stage. Provider setup, notification token, session, network, payload, order routing, and OS presentation remain separate. Do not create or change an order to test notifications; contact the project operator.
iOS asks for persistent notifications
Choose Later to leave the banner style unchanged, or Go to settings once if you intend to review the OS presentation choice. Do not interpret this alert as a request for location or initial notification permission.
Android 10 shows an unexpected permission set
Do not assume the combined set was selected correctly. Record the visible operating-system state without changing it repeatedly and contact the app owner. A type-safe fix and Android 10 platform tests are required before the documentation can claim a complete set.
A feature opens after a denied-looking result
A local gate can advance independently of the effective permission set. Do not use the feature as proof of access or success. Stop before any location, order, notification, or provider action and contact the project operator.
Related guides: Understand location permissions · Sign in as a driver · Understand startup and loading · Driver App overview