Navigation doesn't work properly, if `AutoRouteGuard.onNavigation` method is overridden as async method about auto_route_library

[MartinAKovachev]

Closed, the issue was in another package: https://pub.dev/packages/overlay_support

[Milad-Akarie]

Hey @MartinAKovachev marking navigation as async should not have any effect because the method is not being awaited, the NavigatorResolver is.
what kind of strange behavior are you getting?

[MartinAKovachev]

Hey @MartinAKovachev marking navigation as async should not have any effect because the method is not being awaited, the NavigatorResolver is. what kind of strange behavior are you getting?

Hey @Milad-Akarie,
Ok, if using onNavigation as async is correct, then something else should be the issue. I will keep you updated if we have other questions regarding that topic. The case is that we restart our app by using RestartWidget in which we update the key (so the rest of the tree will be updated) and it is a root widget above the MaterialApp widget. But for some reason the onNavigation is called 2 times with / path when we restart the tree, but we see a white screen instead of / main route. Seems like an old instance of router is being used, but still can't find the reason for happening.
If we immediately call resolver.next() without awaiting anything before that, then it navigates to the / main route (again onNavigation is called 2 times but at least it works).