Turns out the issue was related to navigation between pages, when navigating between pages (e.g., from HomePage to ProfilePage or UsersPage), new pages were added to the navigation stack. This caused problems after logging out or loggin in, as the previous pages remained in the stack, preventing the correct redirection to the login screen.

Solution Implemented: Replacing Navigator.pushNamed with Navigator.pushReplacementNamed:

The core change was replacing Navigator.pushNamed with Navigator.pushReplacementNamed for navigation between HomePage, ProfilePage, and UsersPage. Why the change? Navigator.pushNamed adds a new page to the navigation stack, which can cause issues when navigating back. On the other hand, Navigator.pushReplacementNamed replaces the current page with the new one, ensuring that the navigation stack is not cluttered with extra pages. This solved the issue of the user being stuck on previous pages after logout. Updating the logout method to reset the stack:

The logout method was updated to use Navigator.of(context).pushNamedAndRemoveUntil('/', (route) => false) after logging out. What does this do? This clears the entire navigation stack and redirects the user to the root (AuthPage), ensuring that no previous pages are left behind in the stack. This allows for proper redirection to the login screen after logout. Handling authentication in AuthPage:

AuthPage continues to use StreamBuilder to listen for changes in the authentication state. It automatically redirects the user to HomePage if they are logged in, or to the login/register page if they are logged out. Explanation of the navigation stack issue: Before: When using Navigator.pushNamed, each navigation added a new page to the stack. If the user logged out from a page like ProfilePage or UsersPage, the previous pages remained in the stack, and this caused unexpected behavior when attempting to navigate back to the login screen.

After: By using Navigator.pushReplacementNamed, the current page is replaced with the new one, preventing unnecessary pages from accumulating in the stack. This allows for a clean navigation flow and correct redirection after logout.

This solution resolved the issue by managing the navigation stack correctly, ensuring the user is always redirected to the login screen after logout, without unwanted pages remaining in the stack.