Conversation
ChangelogFeatures
Bug fixes and improvements
Known issues
|
| @@ -0,0 +1 @@ | |||
| - In case an app provides custom `Router` implementation to Nav SDK, the Nav SDK doesn't trigger `NavigationRouteAlternativesObserver` with online alternatives when current route is offline. | |||
There was a problem hiding this comment.
Is it really so? I thought it was more like "it's triggered, but much later". The alternatives mechanism is still working, right? we just won't trigger an alternative request as soon as the network is back.
There was a problem hiding this comment.
@averkhaturau, can you please clarify consequences of using custom router for offline-online switch?
There was a problem hiding this comment.
NN knows which router is online only if it creates the routers itself. Providing a custom router makes this information unavailable, we don't know how to create an online router anymore. That's why the back online feature will not be available with a custom router
| // on implementation details in some cases like offline-online switch. | ||
| // Meanwhile platform SDK uses its own instance of native router for | ||
| // route requests | ||
| null |
There was a problem hiding this comment.
We also pass nativeRouter in recreate method. It should also be null.
There was a problem hiding this comment.
nice one! fixing in a followup PR
Description
Screenshots or Gifs