[$2000] BUG: unread indicator count is not reset after logout reported by @parasharrajat

[kavimuru]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

1. Open the app on web.
2. Login with any account that has some unread messages. (to get unread messages send some messages from a different account to the account being logged in).
3. Now wait a couple seconds.
4. Observe there are unread message count on the Tab.
5. Do not go to the chat that has unread messages.
6. Now Sign out.
7. Wait a couple seconds.
8. Unread count is shown back after log out.

Optional:
9. If count is not shown by step 8, login back with the same account without refreshing the page.
10. Wait for the count to show up.
11. Log out now.
12. Wait a couple seconds, observe the Unread count on the tab bar.

Expected Result:

No unread count and indicator is shown after logout

Actual Result:

Unread count and indicator are shown after logout on login page.

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Web
• iOS
• Desktop App

Version Number: 1.2.12-2
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/194615034-efb34a05-7dfd-4644-b813-d49dbc39827d.mp4

Recording.639.2.mp4

Expensify/Expensify Issue URL:
Issue reported by: @parasharrajat
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1665066610938259

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @tjferriss (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

[tjferriss]

I'm going to pass this over to engineering as I think it's a pass. However, I am on the fence as to whether this issue really hits the value part of the review:

Value — in other words, why is this particular issue important? Are there reasonable workarounds? Is the value of resolution greater than the resources required to reach it?

This seems like a polish item and if it requires more than a super small amount of work then I'd suggest we pass for now.

[melvin-bot]

Triggered auto assignment to @Justicea83 (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[Justicea83]

This can be external, we set the unreadCount on the Web App here.