Use the delivery map
Map view can place the Driver, businesses, and customers for returned active orders on one map. Use it to orient yourself within an order you are authorized to handle. A marker is presentation of the current App state; it is not proof that a position is fresh, precise, trusted, shared, or accepted by another system.
:::warning Opening Map view can start location and network work
Opening or refocusing the map can read active orders, request the device's current position, start location watching, load map or image providers, and request a Driver-position update. Do not open the map repeatedly to test tracking, sharing, or provider availability.
:::
Availability
The Map view tab is part of the signed-in Driver navigation. When Driver App's location-permission gate does not pass, the tab can show a permission explanation instead of the map. See Understand location permissions before changing device access.
Even with the tab available, the map surface depends on a usable initial device position. A blank or unresolved surface does not prove that no active orders, locations, or permissions exist.
Open this capability
Open Map view once for an authorized delivery and wait for the current surface to settle. The map can present:
| Map item | Current-source purpose | Important boundary |
|---|---|---|
| Your Location marker | Shows the latest Driver position held by this map view | It does not certify freshness, accuracy, mock status, background tracking, or server acceptance |
| Business marker | Groups returned active orders by business | The marker coordinate comes from returned order/business data, not a live business-location check |
| Customer marker | Groups returned active orders by customer | The marker coordinate comes from returned order/customer data, not a live customer-location check |
| Marker callout | Shows participant/order context and a link to more order information | Names, addresses, order numbers, and images are sensitive operational data; do not copy or share them |
| + and − controls | Change the local map zoom | Zoom changes presentation only |
Selecting a marker opens its callout. A callout for one order can lead to that order's details; a grouped callout can lead to the order list. Navigation does not confirm assignment, location validity, or delivery progress.
States and variations
| Visible state | Safe interpretation |
|---|---|
| Permission explanation | The local permission gate did not allow the map surface; no effective permission result is inferred |
| Blank or unresolved map area | Initial position, order read, provider, image, permission, or lifecycle work may be unresolved |
| Driver marker only | The map has a nonzero initial Driver position but no order marker passed the current grouping/display conditions |
| Business and customer markers | Returned active-order data produced marker groups for both participant types |
| Several order numbers in a callout | More than one returned order shares that participant grouping key |
| One order in a callout | The marker represents one returned order and can route to its details |
| Marker at an unexpected place | Returned coordinates can be absent, invalid, zero, stale, or otherwise unsuitable; marker visibility is not validation |
| Error alert | One map-controller operation returned or threw an error |
| Changed marker after an App event | The map requested its current order-location data again |
The inspected map logic groups a fixed source-selected set of active order statuses. It is not a complete delivery-state contract, and the displayed markers can change with returned data.
Effects and boundaries
Keep these stages separate when interpreting Map view:
- The tab became focused.
- Driver App requested active-order data.
- A location provider returned a candidate device position.
- Local markers were grouped and rendered.
- Driver App requested a Driver-position update.
- A backend or socket accepted, stored, or distributed location data.
An earlier stage does not prove a later one. This guide does not verify location sharing, order tracking, provider success, server storage, socket delivery, or customer visibility.
Troubleshooting
Map view shows the permission explanation
Follow Understand location permissions. A return from device Settings is not proof that every required permission became effective; wait for Driver App to recheck the current state.
The map remains blank
Wait for the current position and map surface to settle. Confirm device location services and connectivity without repeatedly leaving and reopening the tab. Repeated focus can start more reads and location work.
A marker is missing or appears incorrect
Confirm that you are viewing the authorized order and use its order details as the primary operational context. Do not treat the map as proof of a person's or business's live position. Use the location-validation state shown by the app before treating the marker as usable.
A callout opens the order list instead of one order
A participant marker can group several returned orders. Use the order information in Driver App to select the intended authorized order. Do not copy operational identifiers from the callout.
The map shows an error
Close the alert once and check the current order outside the map. Do not reopen Map view or repeat a location-dependent action to determine whether an earlier read or position update settled.
Related guides: Understand location permissions · Navigate the Driver App · Understand an active delivery · Accept a delivery request