Shan Ma

Hi @DavidKasprzyk and @RRuais , thanks for the feedback, this issue could be reproduced with the single `MapView` from the following steps: 1. Open the `Examples` App of https://github.com/mapbox/mapbox-maps-ios, build...

@DavidKasprzyk In fact we could apply the `MapView.location.options.distanceFilter` to reduce the redraw frequency manually. Because if we display user location, we allow the `MapView` to be updated with the location....

Close this Pr because the arrival event should be triggered by the navigator side.

In fact we noticed this issue since we adopted Nav Native 78.0.0 as in the [slack](https://mapbox.slack.com/archives/C220EHL3W/p1634678852405800 ) .

I've checked that it's nothing to do with the simulation mode. After the navigation service ends, we create a new `NavigationMapView`, and set `PassiveLocationProvider` to its `mapView` to override. But...

And the cause seems to be that the navigator as the `NavigatorObserver` keeps observing location update even after the navigation service ends and the user is still in location in...

Hi @etl , could you take a look at this issue? We've observed the issues related with our navigator as following: 1. when user is still, the `NavigatorObserver` keeps receiving...

Right now in our example, when we [cancel](https://github.com/mapbox/mapbox-navigation-ios/blob/03523ae1a59e8949bf20fa09b2e6ee25ef5a05d5/Example/ViewController.swift#L555-L559) or end the navigation session, we nil out the `NavigationViewController` and [stop](https://github.com/mapbox/mapbox-navigation-ios/blob/03523ae1a59e8949bf20fa09b2e6ee25ef5a05d5/Sources/MapboxNavigation/NavigationViewController.swift#L328-L330) the navigation service.

@mapbox/navigation-ios I think we should unsubscribe from the observer when the user location is still. The simulated status sending from the background causes the rerouting event and a seconds-delay at...

@S2Ler Right now we nil out the `NavigationMapView` for route preview after the active navigation session starts in our `Example`, but because the navigator stills sending simulated navigation status to...