Why is there an increase in both trip time and distance?
A large spike in the expected distance and time often indicates that the driver deviated from the route, chose an alternate route, or added a stop. For more information on added stops, see Handle added stops.
Why is the ETA different from the Directions API (Legacy) or Routes API?
Google Maps or Waze may calculate a different route from the Directions API (Legacy) or Routes API depending on your selected parameters or due to traffic conditions changing after the API call.
Because Navigation Connect continuously calculates the route using the driver's real-time position, it usually provides more accurate ETAs.
Why did the ETA jump suddenly?
Sudden changes in the ETA occur for several reasons:
- Real-world conditions: Traffic, road closures, or other external events can affect the ETA. These conditions typically don't affect the expected distance unless Google Maps or Waze calculates a reroute.
- Driver actions: The driver might deviate from the route, choose an alternate route, or add a stop. These actions typically change both the expected distance and the remaining time. For more information on added stops, see Handle added stops.
Why does the trip status show SUSPENDED when distance or time remains?
This status appears when the driver ends the trip early, such as by exiting
navigation or closing the navigation app. For more information on the
SUSPENDED status, see Handle trip end states.
To help the driver reach their intended destination, provide a button or link in your app that lets the driver resume the Navigation Connect session to the same destination. For more information about mid-trip app switching, see Handle mid-trip app switching.
Does Navigation Connect affect battery life?
No. Navigation Connect doesn't consume more battery life than a standard navigation session on Google Maps or Waze.
Is Incognito mode supported?
No. Navigation Connect does not support Incognito mode in Google Maps. If the driver is in Incognito mode, the app displays an error and the session fails to start.