Thread – New message button and green line appears when go back to main chat from thread

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.40-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5006354
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team

Action Performed:

1. Go to https://staging.new.expensify.com/
2. Log in
3. Open any chat and send 10 messages
4. Right click on the firs message and select Reply in thread
5. Send a comment in a thread
6. Go back to main chat via header link

Expected Result:

New message button not appears

Actual Result:

New message button and green line appears

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6615280_1727297502147.New_message_button_and_green_line_appears_when_go_back_to_main_chat.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @marcaaron (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

Triggered auto assignment to @RachCHopkins (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[github-actions]

👋 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.

[marcaaron]

This looks like the most likely culprit: https://github.com/Expensify/App/pull/49367/files

[klajdipaja]

@marcaaron I doubt that's the culprit because this issue has been reported previously in #49525 a week before #49367 was merged

[marcaaron]

cool! I based my guess entirely on the name of the PR.

[c3024]

The unread marker appearing on coming back from thread is fixed with this PR #49770. That can be CPed to staging.

[AndrewGable]

@dangrous says this one is fixed via the CP!