[Bug]: IOS Navigation not starting

[rajeshbdabhi]

Is there an existing issue for this?

• I have searched the existing issues

Description of the bug

In IOS navigation not starting but in android it is working fine.

when i set destination nothing happend because that method does not returning any status and stuck at that function

final Destinations msg = Destinations(
      waypoints: <NavigationWaypoint>[
        NavigationWaypoint.withLatLngTarget(
          title: 'Grace Cathedral',
          target: const LatLng(latitude: 20.825563, longitude: 71.042010),
        ),
      ],
      displayOptions: NavigationDisplayOptions(),
    );
    
    final NavigationRouteStatus status =
        await GoogleMapsNavigator.setDestinations(msg);

    if (status == NavigationRouteStatus.statusOk) { }

Flutter version

3.29.2

Package version

0.6.2

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.29.2, on macOS 15.5 24F74 darwin-arm64, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
[!] Xcode - develop for iOS and macOS (Xcode 16.4)
! CocoaPods 1.15.0 out of date (1.16.2 is recommended).
CocoaPods is a package manager for iOS or macOS platform code.
Without CocoaPods, plugins will not work on iOS or macOS.
For more info, see https://flutter.dev/to/platform-plugins
To update CocoaPods, see https://guides.cocoapods.org/using/getting-started.html#updating-cocoapods
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.3)
[✓] VS Code (version 1.101.1)
[✓] Connected device (5 available)
[✓] Network resources

! Doctor found issues in 1 category.

Steps to reproduce

just run app into IOS navigation not starting because status not come from GoogleMapsNavigator.setDestinations function

Expected vs Actual Behavior

in IOS also should give status from final NavigationRouteStatus status = await GoogleMapsNavigator.setDestinations(msg); this line

Code Sample

// Example code here

Additional Context

No response

[rajeshbdabhi]

@jokerttu here i attached video of issue

https://drive.google.com/file/d/1s3g1n-urGCcTbJnHuiZqFhYQ9t5qpVIQ/view?usp=drive_link

[sonhoang-diqit]

@rajeshbdabhi You can try to downgrade to version 0.6.0.

[rajeshbdabhi]

@sonhoang-diqit i checked with your suggestion still issue not resolved i identified issue this issue comes only with ios and if i use background_locator_2 plugin.

[illuminati1911]

@rajeshbdabhi Thanks for reporting the issue.
Did I understand correctly that you also have the same issue on 0.6.0?

[rajeshbdabhi]

@illuminati1911 yes i have same issue in 0.6.0 version

[illuminati1911]

@rajeshbdabhi

1. Did you set your API key correctly on the iOS side?
2. Did you ask user to accept terms and conditions?
3. Did you ask location permission from the user?
4. Did you initialize the navigator?

[rajeshbdabhi]

@illuminati1911

1. Did you set your API key correctly on the iOS side? => YES
2. Did you ask user to accept terms and conditions? => YES
3. Did you ask location permission from the user? => YES
4. Did you initialize the navigator? => YES

yes i did all checks and as i told earlier all things are working fine in android and only not working in ios when i use background_locator_2 plugin and call await BackgroundLocator.initialize(); this method after when i start navigation it is not drawing any route or header or footer. if i remove background_locator_2 this plugin or do not initialize then navigation working fine in ios same like android without any error or issue.