[$500] Web - IOU-After refreshing page green dot disappears in LHN chat

[izarutskaya]

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

---

Version Number: 1.4.11
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal Team
Slack conversation: @

Action Performed:

1. Go to https://staging.new.expensify.com/ as user A
2. Tab fab
3. Tap request money--- manual
4. Enter an amount
5. Tap next
6. Select user B
7. Tap request
8. Login as user B
9. Note green dot on 1:1 chat
10. Refresh the page

Expected Result:

The green dot on chat in LHN must not disappear after refreshing the page.

Actual Result:

The green dot on chat in LHN must not disappear after refreshing the page.

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6310338_1702380565800.green.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01b698715da7076ac6
• Upwork Job ID: 1734544059387871232
• Last Price Increase: 2024-01-05

[melvin-bot]

Triggered auto assignment to @laurenreidexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01b698715da7076ac6

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @situchan (External)

[unidev727]

@izarutskaya
The actual result and expected result are same.

[bernhardoj]

Should be fixed in #32590.

OpenApp is called after refresh and it returns the old report data.

[melvin-bot]

@laurenreidexpensify, @situchan Huh... This is 4 days overdue. Who can take care of this?

[laurenreidexpensify]

hold on #32590

[laurenreidexpensify]

#32590 will be on prod for 7 days tomorrow

[melvin-bot]

@laurenreidexpensify, @situchan Huh... This is 4 days overdue. Who can take care of this?

[melvin-bot]

@laurenreidexpensify, @situchan Still overdue 6 days?! Let's take care of this!

[laurenreidexpensify]

@situchan @bernhardoj can you confirm if this is still reproducible now that #32590 is fixed?

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[melvin-bot]

@laurenreidexpensify, @situchan Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

@laurenreidexpensify, @situchan Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[laurenreidexpensify]

@Expensify/applauseleads can you confirm if this is reproducible in KI testing this week thanks

[melvin-bot]

@laurenreidexpensify @situchan this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ and will need to go internal. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks!

[laurenreidexpensify]

@applausebot @Expensify/applauseleads can you confirm if this is reproducible in KI testing this week thanks

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸