[Bug]: multiple api calls

[Mahmoud-Sabry153]

Is there an existing issue for this?

• I have searched the existing issues

Description of the bug

🧩 Description of the Issue

Previously, I used setDestination with three waypoints and managed navigation progression using continueToNextDestination.

Since continueToNextDestination is now deprecated, I’ve switched to calling setDestination each time I need to move to the next waypoint by providing the updated list of waypoints.

My question is: does this approach trigger a new navigation request each time setDestination is called — meaning that navigating through the three waypoints would result in three separate API calls to the navigation service?

My app is currently live in production, and this behavior directly affects how navigation works for real users.

Could you please confirm whether calling setDestination multiple times (after the deprecation of continueToNextDestination) will trigger new navigation API requests each time, or if it will reuse the existing route context internally?

I’d really appreciate a clear answer or official clarification on the expected behavior — it’s quite important for ensuring a smooth experience in the live app.

Thank you for your work on this package! 🙏

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

🚀 Steps to Reproduce

Use setDestination with three waypoints.

Previously, call continueToNextDestination to move to the next point.

Now, since it’s deprecated, call setDestination again for each waypoint with updated parameters.

Expected vs Actual Behavior

✅ Expected Behavior

Navigation should continue smoothly between waypoints without triggering multiple navigation API requests.

❌ Actual Behavior

Unclear whether each call to setDestination initiates a new navigation API request, potentially leading to three separate route requests.

Code Sample

//

Additional Context

No response

[illuminati1911]

Hi @Mahmoud-Sabry153 . 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.