Csongor Keller

thanks @ShanMa1991 I've tried your workaround but as I thought It's not working, since it has the 25 limit. `Error matching coordinates: invalidInput(message: Optional("Too many coordinates; maximum number of coordinates...

Thanks for the response @1ec5 but this doesn't work either. Since the option in response is a `ResponseOptions` and `MapboxNavigationService` wants `RouteOptions`. So I can not simply use the response...

please find the project here: https://github.com/csongorkeller/flutter_mapbox_navigation/blob/master/ios/Classes/SwiftFlutterMapboxNavigationPlugin.swift

Great @1ec5, many thanks for this. Although when starting the navigation at the end, I haven't found a workaround for how to assign a `NavigationMatchOption` to `NavigationViewController(routeOptions:)` as it works...

Thanks @1ec5 this did the trick, Although now I'm facing another small problem. Well, actually 2 of them. 1. When assigning the route to navigation, I got back a lot...

@1ec5 Do you have any idea why the above-mentioned behavior appears? I haven't found anything mentioning this problem... Thanks in advance

@1ec5 I think the above mentioned issues are still related to mapmatching and navigation. Hereby the request when I got back submatches although the backend uses cycling as profile and...

And here is a case when there are valid coordinates but receive NoMatching back for some reason. Coordinates: ``` [__C.CLLocationCoordinate2D(latitude: 51.5344949, longitude: -0.0782042), __C.CLLocationCoordinate2D(latitude: 51.5362409, longitude: -0.0736132), __C.CLLocationCoordinate2D(latitude: 51.5397824, longitude:...