Dev: Mark as unread not working when request money for workspace

[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. Click FAB => request money
2. Input amount => next
3. Select a workspace => request
4. Hover on message request money click mark as unread, Observe that the message is not marked unread.

Expected Result:

Message is marked unread

Actual Result:

Message is not marked unread

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

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

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• [x ] MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: dev
Reproducible in staging?: dev
Reproducible in production?: dev
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
Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:
Issue reported by: @namhihi237
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1691027823277929?thread_ts=1691027823.277929&cid=C049HHMV9SM

View all open jobs on GitHub

[melvin-bot]

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

[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

[OSBotify]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

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

[namhihi237]

Videos reproduce

Screen.Recording.2023-08-03.at.08.57.13.1.mov

[Beamanator]

@vitHoracek @Julesssss @luacmartins this is all still under beta, right? So probably NAB?

[Beamanator]

Marking NAB for now due to ^

[dangrous]

Seems like this can just be a regular external issue, I think?

[rushatgabhane]

even weirder, why is there an option to "Pay" when the workspace owes you money

[melvin-bot]

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

[maddylewis]

@dangrous - since this is happening on Dev, we will need an engineer to reproduce this one! will you lmk if it's still reproducible whenever you have a sec?

if it is, we can add the External label and go from there 👍

[maddylewis]

heya @isabelastisser - i am OOO until ~Aug 20. I am waiting for a response to my question here - #24112 (comment)

depending on @dangrous's response, we can get the External label added and treat this like any standard bug issue 👍

[dangrous]

im not able to reproduce on latest main - I asked in Slack if the reporter is still able to reproduce

[dangrous]

@namhihi237 also cannot reproduce, so we're going to close