When no account is active, ensure that the root level route is always choose-account page #1369
Labels
a-api
Implementing specific parts of the Zulip server API
Milestone
This can happen if the account is logged out on a non-
AccountRoute
route. Normally this would be a page reachable from logged in account, such as "About Zulip" page.When that happens, routes to be removed on logged out are removed, leaving only the "About Zulip" page on the navigator stack. Since the navigator stack is non-empty, the choose-account page route is not pushed onto the stack. The symptom is that the user can no longer log into another account.
Assigned a higher priority because this bug is relatively easy to reproduce:
Related:
The text was updated successfully, but these errors were encountered: