S2Ler
S2Ler
@1ec5 This look ok to me although we need new tests to cover this functionality
A note: Pause/resume is controlled for billing purposes as well. Simply calling pause/resume from another place will likely to produce undefined behavior.
> The simulated status sending from the background causes the rerouting event and a seconds-delay at the start of active navigation in our `Example` App. @ShanMa1991 Can you please clarify...
> For the pause/resume, it would be one way to provide a fix to avoid the simulated location updates while user is still. But how could we stop dealing with...
> Several crashes are observed related with the unsynced `routeProgress` which triggers the `precondition` failure, when we start and cancel navigation several times. I still not able to reproduce this...
> But right now the map puck shows the user is moving, and there's constant location update about the user. @ShanMa1991 Does this happens only after simulated active drive?
> user is still By user is still, do you mean that we don't provide locations to Native Navigator or that we provide the same location every second?
Would love to see tests for the new functionality.
This issue is no longer blocked and can be implemented.
@jimhill what Navigation SDK version do you use?