[Bug]: deprecated continueToNextDestination

[Fares-fa]

Is there an existing issue for this?

• I have searched the existing issues

Description of the bug

I was using setDestination with three waypoints, and then using continueToNextDestination to make the navigation proceed to the next point.

Now that continueToNextDestination is deprecated, I need to call setDestination each time I want to update the route, providing the updated waypoints.

My question is: will this trigger a new navigation request each time — meaning the three points will result in three separate navigation API calls?

Flutter version

3.35.1

Package version

0.6.5

Native SDK versions

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

Flutter Doctor Output

[√] Flutter (Channel stable, 3.35.1, on Microsoft Windows [Version 10.0.19045.6332], locale en-US)
[√] Windows Version (10 Enterprise 64-bit, 22H2, 2009)
[√] Android toolchain - develop for Android devices (Android SDK version 36.0.0)
[√] Android Studio (version 2024.3)
[√] Connected device (3 available)
[√] Network resources

Steps to reproduce

I was using setDestination with three waypoints, and then using continueToNextDestination to make the navigation proceed to the next point.

Now that continueToNextDestination is deprecated, I need to call setDestination each time I want to update the route, providing the updated waypoints.

My question is: will this trigger a new navigation request each time — meaning the three points will result in three separate navigation API calls?

Expected vs Actual Behavior

.

Code Sample

// Example code here

Additional Context

No response

[Fares-fa]

@jokerttu can i know if am right or not?

[Mahmoud-Sabry153]

@jokerttu is that true that it consume one navigation request call each time i call setdestination?

[illuminati1911]

Hi @Fares-fa and thank you for opening the issue.

This depreciation follows the native iOS SDK, where this method is also deprecated: https://developers.google.com/maps/documentation/navigation/ios-sdk/reference/objc/Classes/GMSNavigator#-continuetonextdestination

Up-to-date triggers for billable events are visible here: https://developers.google.com/maps/billing-and-pricing/sku-details#navigation-request-ent-sku

Note that you can still use the continueToNextDestination method, even though it is marked as deprecated.