[Bug]: Wrong data in NavInfo

[lazar89nis]

Is there an existing issue for this?

• I have searched the existing issues

Description of the bug

When continueToNextDestination is called in a multi-destination navigation flow, OnNavInfoEventCallback starts to get corrupted data. It's mixing remainingSteps and shows weird data that is not correct.

This is making displaying steps or calculating distance wrong, so I get a blink in UI until data gets fixed after one or two OnNavInfoEventCallbacks.

Flutter version

3.35.3

Package version

0.6.4

Native SDK versions

• I haven't changed the version of the native SDKs

Flutter Doctor Output

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.35.3, on macOS 15.3 24D60 darwin-arm64, locale en-RS)
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 16.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2025.1)
[✓] VS Code (version 1.97.2)
[✓] Connected device (6 available)
! Error: lazar’s iPad has recently restarted. Xcode will continue when lazar’s iPad is unlocked. (code -14)
[✓] Network resources

• No issues found!

Steps to reproduce

1. Add multiple destinations using setDestinations (for example 2)
2. Start navigation and when setOnArrivalListener is triggered call GoogleMapsNavigator.continueToNextDestination()
3. observe OnNavInfoEventCallback before and after continueToNextDestination call

Expected vs Actual Behavior

Before continue action:
navInfo.currentStep
stepNumber: 3, distanceFromPrev: 662, fullInstructions:
navInfo.remainingSteps
stepNumber: 0, distanceFromPrev: 0, fullInstructions: Head north on Zetska towards Dušana Popovića
stepNumber: 1, distanceFromPrev: 656, fullInstructions:

After continue action:
navInfo.currentStep
stepNumber: 0, distanceFromPrev: 0, fullInstructions: Head west on Igmanska
navInfo.remainingSteps
stepNumber: 1, distanceFromPrev: 129, fullInstructions: Turn left to stay on Igmanska (*this steps is already done)
stepNumber: 2, distanceFromPrev: 76, fullInstructions: Turn right onto Zetska (*this steps is already done)
stepNumber: 3, distanceFromPrev: 662, fullInstructions: (*this steps is already done)
stepNumber: 0, distanceFromPrev: 0, fullInstructions: Head north on Zetska towards Dušana Popovića
stepNumber: 1, distanceFromPrev: 656, fullInstructions:

After 2 more OnNavInfoEventCallback events state gets back to normal:
navInfo.currentStep
stepNumber: 0, distanceFromPrev: 0, fullInstructions: Head north on Zetska towards Igmanska
navInfo.remainingSteps
stepNumber: 1, distanceFromPrev: 710, fullInstructions:

Code Sample

//Set user location to something like: 43.304447, 21.912585

    List<NavigationWaypoint> waypointsList2 = [
      NavigationWaypoint.withLatLngTarget(
        title: "Waypoint 1",
        target: LatLng(
          latitude: 43.30580381,
          longitude: 21.91264903,
        ),
      ),
      NavigationWaypoint.withLatLngTarget(
        title: "Waypoint 2",
        target: LatLng(
          latitude: 43.31158066,
          longitude: 21.91121307,
        ),
      ),
    ];

    final Destinations destinations = Destinations(
      waypoints: waypointsList2,
      displayOptions: NavigationDisplayOptions(showDestinationMarkers: false),
      routingOptions: RoutingOptions(
        travelMode: NavigationTravelMode.driving,
        alternateRoutesStrategy: NavigationAlternateRoutesStrategy.none,
      ),
    );

Additional Context

Another thing that is wrong with NavInfo is the data for:
/// The estimated remaining distance in meters to the final destination which
/// is the last destination in a multi-destination trip.
final int? distanceToFinalDestinationMeters;

/// The estimated remaining time in seconds to the final destination which is
/// the last destination in a multi-destination trip.
final int? timeToFinalDestinationSeconds;

From docs it should have the distance from the last destination in multi-destination trip, but it's returning data to the first upcoming destination.

[illuminati1911]

@lazar89nis Thank you for reporting the issue. We'll take a look.
Did I understand correctly that this happens on both iOS and Android?

[jokerttu]

@lazar89nis

Could you please test if removing the first waypoint from the list and then calling setDestinations again with the updated set of waypoints works, instead of calling continueToNextDestination?

continueToNextDestination is deprecated method inside navigation SDK. We are currently updating documentation (example) to use the new recommended way to continue on the route.

What continueToNextDestination does internally:

Pops the first destination from the current list of destinations. Following this call, guidance will be toward the next destination, if any

And what is suggested behaviour on deprecation message:

Call one of the -setDestinations:... methods with the new list of destinations instead

Could you please let us know if this fixes the issue?
Thank you for reporting this!

[lazar89nis]

Sure, I will redo my code and test it. Can you just let me know, should I stop navigation, or can I just pop a waypoint and call setDestinations?

[jokerttu]

@lazar89nis
It should not be mandatory to call startGuidance again as it is already running, and it automatically detects changing route on fly.
If you use simulation for debugging purposes, it is important to start simulation again on existing route to be sure it simulates through current updated existing route.

[lazar89nis]

I am not using simulation as I have everything set up and have RocketSim that I am using to fake location. Will reply during the day if this fixes the problem. It may fix these extra steps that I am getting, but still distanceToFinalDestinationMeters and timeToFinalDestinationSeconds will be wrong for multi-destination tours.

[lazar89nis]

I will need to do one live test to be 100% sure, but from simulations, it looks like setDestinations works well. I don't have mixed information inside NavInfo, and I think it has nicer UX. When I was using continueToNextDestination it had some strange jump in the camera.

[jokerttu]

Thank you for this information,
I will create PR that more clearly deprecates the continueToNextDestination method call, and also updates example apps.
We will also check if there is way to get info about distance and time to different waypoints on multi-destination routes.

[lazar89nis]

If there is no way to get the right data, maybe you should just change the documentation description for the field. There is a way to calculate it by hand, I am just looking at the remainingSteps and timeToCurrentStepSeconds/distanceToCurrentStepMeters. Looks like this gives me the info I need.

[jokerttu]

@lazar89nis
These fields are provided directly by the native Google Maps Navigation SDKs. I will check the values and conversion layers to ensure everything is handled correctly on the package code before making any decisions.