Fix for initial camera position when snapUserLocationToRoute is enabled #386
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a fix for snapUserLocationToRoute option. When it is enabled on NavigationMapView the camera position is defaulted to Lat: 0.0 Lng: 0.0
This happens even when you have a location provider with an activated listener.
The problem seems to be when the locationEngine.lastLocation is initialized in NavigationMapView. It will check snapUserLocationToRoute option and set the LocationEngines last location to the uiState.snappedLocation.
The problem with this is the current uiState.snappedLocation which when starting the view is null and is not set until navigation has started.
This PR fixes this by simply adding a extra check for isNavigating on the snapUserLocationToRoute option when the LocationEngine lastLocation is initialized.