My Pack

When the user's JWT token expires, a "Token Expired" popup is displayed; however, the user is not redirected to the login screen. Instead, the user remains on the Home screen and is still able to access certain application features and invoke some APIs that modify data.

Once the authentication token has expired, the user's session should be considered invalid. The application should immediately clear the expired session, prevent access to all protected resources, and redirect the user to the login screen to re-authenticate. Allowing users to remain in the application and perform authenticated operations after token expiration poses a security risk and results in inconsistent session handling.

• * Log in to the application with a valid user account.
• Wait until the JWT token expires (or use an expired token).
• Perform any action that triggers an authenticated API request.
• Observe the "Token Expired" popup.
• Dismiss the popup and continue using the application.
  Actual Result
• A "Token Expired" popup is displayed.
• The user remains on the Home screen.
• The expired session is not cleared.
• The user can still access some protected screens and invoke certain APIs that modify data.
  Expected Result
• As soon as the JWT token expires, the application should invalidate the user's session.
• All protected API requests should be blocked.
• Any stored authentication tokens and user session data should be cleared.
• The user should be automatically redirected to the login screen.
• The user should be required to log in again before accessing any protected features or performing any data modification operations.