Closed Zazo032 closed 1 year ago
Code to reproduce the issue:
@Zazo032 it's important to use a consistent navigation system throughout your app. Mixing different navigation systems can lead to conflicts and unexpected behavior. It is not good practice to use more than one navigator in the app. In this way, the package will not be able to communicate with the extra navigator 1 you add separately. So you will need to migrate all your routes to use qlevar to solve this issue.
We're currently migrating our current codebase from older
Navigator.push/pop
to ´qlevar`. Our app currently has 4 main routes, let's call them A, B, C and D, which can only be navigated in order: A->B->C->D.Only routes A and B are migrated to
qlevar
, and from B to D we're still navigating usingNavigator.push/pop
. At this point, I found 2 issues which I'm not sure if are related:qlevar
:initState
is called again@SchabanBo do you have any idea of what could be happening here?