Replies: 3 comments
-
It's probably a good idea to describe how I'm using Voyager (in Android) here. In the main
and then:
Think of the Perhaps this is the problem? The |
Beta Was this translation helpful? Give feedback.
-
It seems the problem is that when the device is rotated, the So that explains what is happening. But this begs the question, where are you supposed to collect such navigation events? Or, is there a way to recreate the backstack of screens? Because it makes more sense that following device rotation the stack should be the same as before device rotation. |
Beta Was this translation helpful? Give feedback.
-
I seem to have found a solution by changing the
Have I stumbled upon the correct way to do this? |
Beta Was this translation helpful? Give feedback.
-
I use a SingleShotEventBus to communicate navigation events to a Composable which, in turn, will push the appropriate screens using the navigator.
In the Composable, I collect these events this way:
However, while this works initially, after screen rotation, it doesn't (nothing is collected).
How to write this properly?
Beta Was this translation helpful? Give feedback.
All reactions