S2Ler
S2Ler
or `.setFailureType`.
@DiegoResnik I wasn't able to reproduce the issue. It looks like an integration issue. If you could provide a sample that has this issue, we would help investigate and guide...
@samcrawford @DiegoResnik If NavigationService isn't deallocated after `NavgiationViewController` dismiss it is a sign of a memory management issue. You can investigate what exactly keeps `NavigationService` alive using [Xcode Memory Graph](https://developer.apple.com/documentation/xcode/gathering-information-about-memory-use)....
@MaximAlien Can you please take a look on this problem?
@DiegoResnik You can actually pass NavigationService to `NavigationViewController` through https://github.com/mapbox/mapbox-navigation-ios/blob/655e2060f852fe1e321b68b290ab35562a2dd30b/Sources/MapboxNavigation/NavigationViewController.swift#L320 or https://github.com/mapbox/mapbox-navigation-ios/blob/655e2060f852fe1e321b68b290ab35562a2dd30b/Sources/MapboxNavigation/NavigationViewController.swift#L306 (using https://github.com/mapbox/mapbox-navigation-ios/blob/655e2060f852fe1e321b68b290ab35562a2dd30b/Sources/MapboxNavigation/NavigationOptions.swift#L47). Will it work? That way it seems you don't need to retain NavigationViewController, it seems. Will...
@1ec5 Shall we make `RouteProgress.legIndex` property `internal(set)`? We already have `RouteController.advanceLegIndex(completionHandler:)` method that is a correct way of advancing a leg index.
More changes are needed. RouteProgress is a reference type and not safe to use from multiple threads.
Thanks, @NathanaelA, for taking your time to report the issue. Unfortunately, I couldn't reproduce the problem using Mapbox Navigation SDK for iOS "2.0.0-beta.9". However, I've attached the example app I...
@NathanaelA I tried to reproduce and investigate this issue but unfortunately hasn't found the cause. Do you still observe the reported issue? Have you tried latest updates?