RouteController.snapsUserLocationAnnotationToRoute purports to affect whether a map view’s user location annotation is snapped to the route. However, Core Navigation doesn’t actually do anything in response to this property; it only affects how RouteMapViewController behaves in the main navigation SDK.
In the Swift example application, CustomViewController sets snapsUserLocationAnnotationToRoute to true with the expectation that it snaps the user puck to the route, but it doesn’t. Instead, CustomViewController implements its own snapping in progressDidChange(_:). So setting snapsUserLocationAnnotationToRoute is a bit misleading.
Additionally, the documentation claims that snapsUserLocationAnnotationToRoute is disabled by default, but it’s actually enabled by default.
/cc @bsudekum @ericrwolfe
RouteController.snapsUserLocationAnnotationToRoutepurports to affect whether a map view’s user location annotation is snapped to the route. However, Core Navigation doesn’t actually do anything in response to this property; it only affects how RouteMapViewController behaves in the main navigation SDK.In the Swift example application, CustomViewController sets
snapsUserLocationAnnotationToRoutetotruewith the expectation that it snaps the user puck to the route, but it doesn’t. Instead, CustomViewController implements its own snapping inprogressDidChange(_:). So settingsnapsUserLocationAnnotationToRouteis a bit misleading.Additionally, the documentation claims that
snapsUserLocationAnnotationToRouteis disabled by default, but it’s actually enabled by default./cc @bsudekum @ericrwolfe