Android navigation doesn't survive process death
FunkyMuse opened this issue · comments
create starting scene A, open scene B from A
minimize the app, then open device explorer > processes > kill process > try to maximize the app, the current scene should be B and when you go back it should open A, instead it's only A
PreCompose is not using SavedStateHandle now, so this is the current behavior, I'll try to add support to this but will be an Android only behavior.
PreCompose is not using
SavedStateHandlenow, so this is the current behavior, I'll try to add support to this but will be an Androud only behavior.
Yes that's totally understandable, only Android needs this AFAIK
@Tlaster is this in progress by you or?
It's kinda crucial for the UX when releasing to the Play Store as many devices kill the apps unexpectedly and the backstack is lost when using PreCompose
@Tlaster is this in progress by you or? It's kinda crucial for the UX when releasing to the Play Store as many devices kill the apps unexpectedly and the backstack is lost when using PreCompose
Sorry, but I am currently ill and may not have time to do this quickly.
@Tlaster is this in progress by you or? It's kinda crucial for the UX when releasing to the Play Store as many devices kill the apps unexpectedly and the backstack is lost when using PreCompose
Sorry, but I am currently ill and may not have time to do this quickly.
I hope you recover quickly, take care!
If you can point me into the way you want this done, I can create a PR.
@Tlaster is this in progress by you or? It's kinda crucial for the UX when releasing to the Play Store as many devices kill the apps unexpectedly and the backstack is lost when using PreCompose
Sorry, but I am currently ill and may not have time to do this quickly.
I hope you recover quickly, take care!
If you can point me into the way you want this done, I can create a PR.
Thanks, I don't have a clue right now. If you want to contribute, feel free to do so.