doubov02/08/2023, 11:28 PM
to 1 does fix the bug, but I'm pretty sure this shouldn't be required. 🙏
get destroyed as well, and we get a new instance when we navigate back to Child A. Is this expected? Should
be set to
to ensure that state is retained for all the components? 🤔
... but I'm still not sure why a new
Child Stack automatically preserves the stack when a configuration change or process death occurs. By default, only the active component is recreated, components in the back stack remain destroyed and are created on demand.
is created when I navigate back to Child A
Arkadii Ivanov02/09/2023, 10:34 AM
to have the behaviour you want, this would also match the behvaiour of Android Fragments.
. I will think about it.
doubov02/09/2023, 4:39 PM
Arkadii Ivanov02/09/2023, 4:41 PM