Save restoration doesn't work when Android destroys activity and create it again.

[Grouen]

When Android destroys activity Voyager serialize screens and then restore them. But they now are different objects and Voyager uses them as "key" for "navigator.stateHolder.SaveableStateProvider" I think that is why Voyager can't restore state after activity recreation. (Same for tabNavigator.stateHolder.SaveableStateProvider(currentTab))

[adrielcafe]

Fixed in 1.0.0-beta04. Updated the docs with instructions.

Thanks again @Grouen !

[Grouen]

@adrielcafe Still doesn't work when use transitions. Default CurrentScreen() works fine. I think issue is here:

   Box(modifier) {
        items.forEach {
            key(it.screen) {
                navigator.stateHolder.SaveableStateProvider(it.screen.key) {
                    it.content()
                }
            }
        }
    }

Voyager should use it.screen.key instead of it.screen for key.
By The Way, maybe default key implementation should be unique? Something like View.generateViewId()

[adrielcafe]

I was unable to reproduce using transitions with "Don't Keep Activities" enabled. But I've done as you sugested, can you validade with 1.0.0-beta05?

About the key, for that to work the key function must be a property. Since Screen is an interface it can't set the value itself, so every screen would have to do something like override val key = generatedUniqueKey(). This can be avoided by change the Screen to an abstract class, but I don't wan't to do that.

I'll keep looking for options, maybe KSP could help. Feel free to open a new issue about that. And if you have any suggestion will be very welcome :)

[Grouen]

I was unable to reproduce using transitions with "Don't Keep Activities" enabled. But I've done as you sugested, can you validade with 1.0.0-beta05?

Issue is fixed, thanks.