Hmm what if you want the login screen to be a navigator, then the default case in the nav reducer wouldn’t navigate when not logged in. A simple solution to this would be to update both of the states on all navigation actions, but that seems a little bit excess to me. Do you have any other suggestion which could help solve that?
Currently I use a stack navigator, where I first ask for a username and the on the next screen the user will either be able to login or create an account, depending on wether the user exists.
Another solution could be to keep the logged in state in the same state slice as the navigation, then you could update one or the other depending on the value of the logged in state.