Open external navigation
Driver App can present an internal order map, a Show in other maps control, and address links. These surfaces can hand destination and current-position data to an external map provider. This procedure stops before selecting a provider or opening an address link.
:::warning External navigation leaves Driver App
Selecting a provider or linked address can open another app with operational address and coordinate data. Provider installation, route calculation, privacy, accuracy, and arrival are outside Driver App. Do not continue merely to test which app opens.
:::
Availability
An order detail can show an internal map control when order/location data and the App's local permission state admit it. Opening the internal map can mount a map provider, read current position, follow location for selected order phases, and load order/customer/business assets.
The internal map can show Show in other maps when it has destination context. The provider chooser receives destination coordinates and can also receive the current Driver coordinates as route origin.
Order details also render some business/customer addresses as direct platform links. These do not use the same chooser:
| Surface | Pre-action boundary |
|---|---|
| Show in other maps | Opens a provider chooser that can inspect available map apps; stop before selecting an app |
| Business/customer address link | Can call the platform map scheme directly; stop before selecting the address |
| Internal map marker | Stays in Driver App, but marker/data/provider state is not route or freshness proof |
Before you start
- Confirm that the order and destination belong to the authorized active delivery.
- Review the displayed business/customer name and address without copying them.
- Resolve location permissions through the dedicated guide; a local gate is not complete OS-grant proof.
- Keep the external handoff closed if the destination, coordinates, assignment, or provider choice is uncertain.
Complete the task
- Open the intended order detail and select its internal map control once.
- If Request permissions or a blocked-location message appears, stop. Do not open Settings as part of this procedure.
- In the internal map, review the destination label/marker and current order context. A rendered marker is not proof of a valid, fresh, or reachable destination.
- Locate Show in other maps, but do not select it in this procedure. That selection can begin installed-app/provider discovery.
- Do not select a linked address in order details. Address text can invoke the platform map scheme without showing the same provider chooser.
- If a provider chooser is already open, select Cancel. Do not choose a map app while following this pre-action guide.
The operational handoff begins only after an authorized Driver deliberately selects an external provider or direct address link. That action and everything after it are outside this article.
Verify the result
The safe result is limited to one of these states:
| Observable state | Safe interpretation |
|---|---|
| Internal map visible | Driver App rendered local/provider map state; no external route exists yet |
| Show in other maps visible | A chooser entry control is available; no installed app or route is proved |
| Provider chooser visible | App/provider enumeration was attempted; no provider was selected or opened |
| Chooser cancelled | The local chooser closed; no external-navigation completion is implied |
| Address remains in Driver App | The direct platform link was not selected |
| Unsupported-link alert | The platform adapter could not open the supplied link; no provider state is established |
No safe result in this guide proves that a map app is installed, that a route was built, or that the Driver reached the destination.
States and variations
Provider chooser
The map-link chooser can inspect installed providers and is configured to include Google as an option. A visible Google entry is not proof that Google Maps is installed. Other entries depend on platform, package declarations/queries, library behavior, installed apps, and current device state.
iOS and Android links
Direct address links use an Apple Maps-style scheme on iOS and a geo scheme on Android. Native source lists/query declarations for many providers, but a declared scheme is not an installed-app, supported-link, or successful-open receipt.
Address and coordinate quality
Business address, address notes, and customer address can be used to build platform links with returned latitude/longitude. Missing, string, zero, stale, or mismatched data can still produce a link-looking control. Driver App does not validate route quality by rendering the address.
Internal map lifecycle
Opening the internal DriverMap can request GPS, start/stop a location watch, fit coordinates, calculate local distance/time estimates, and load the Google map provider. These stages are not external-navigation or route completion.
Troubleshooting
Show in other maps is missing
The internal map/destination/provider state may be incomplete. Do not tap an address as a workaround. Verify the authorized order and ask the dispatcher to confirm destination data.
The chooser lists an unexpected provider
The list depends on library discovery, platform declarations/queries, installed apps, and the always-include option. Cancel the chooser; do not select a provider to test installation.
An address link shows unsupported
Do not edit the address or try alternate schemes from Driver App. Return to the order and ask the dispatcher to verify the destination and approved navigation provider.
The internal marker or distance looks wrong
Do not start external navigation. Marker, GPS, speed, distance and returned address can be stale or invalid. Review Understand location permissions and escalate the destination.
An external map opened accidentally
Do not start guidance or change the destination. Return to Driver App when safe and verify the order before any further handoff. The external app opening is not route or delivery completion.
Related guides: Use the delivery map · Understand location permissions · Understand Driver permissions · Understand an active delivery