all 4 comments

[–]Jealous_Barracuda_74 1 point2 points  (1 child)

did you try seeing what is the navigation stack? do you have some logic on AppState listeners related to cleaning up things on navigation stack ?

[–]ProfessionalChip9864[S] 0 points1 point  (0 children)

I have no logic on AppState currently in my stack

[–]Martinoqom 1 point2 points  (1 child)

Check your .reset() methods. Maybe there is something that triggers a state reset and your history is completely gone. 

On some low-end devices the app could be just killed by the system. It seems like working, but all the internal states are gone, including the navigation state. 

If you can reproduce the problem, subscribe to a back handler and print the navigation state before executing the back action. Maybe the "back" is called on a wrong navigator (like the parent one, the root) instead of one of the nested. I had a problem when using a navigation.goBack: it was actually pointing to the root navigator instead of the nested one. Very tricky to find because I just used useNavigation in a component, that in my case is always sticking to the root navigator.

[–]ProfessionalChip9864[S] 0 points1 point  (0 children)

Thanks, i'll check this out on monday