Skip to content

[Due for payment 2025-09-19] Chat - New message button appears and disappears when returning from thread for the second time #68327

Closed

Description

@jponikarchuk

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: 9.1.93-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #66683
Email or phone of affected tester (no customers): sndoijsodsiod@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Chat Report View

Action Performed:

  1. Go to staging.new.expensify.com
  2. Open a new 1:1 DM (no chat history).
  3. Send a message to the user.
  4. Right click on the message > Mark as unread.
  5. Right click on the message > Reply in thread.
  6. Click on the blue Thread above the parent message.
  7. Note that no New message button appears.
  8. Right click on the message > Reply in thread.
  9. Click on the blue Thread above the parent message.

Expected Result:

There will be no New message button after returning from thread for the second time.

Actual Result:

New message button appears and disappears when returning from thread for the second time.

**If we use browser back button to return to main chat from thread, new message button also appears and disappears.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @sonialiap

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Aug 12, 2025
  2. melvin-bot commented on Aug 12, 2025

    @melvin-bot

    Triggered auto assignment to @sonialiap (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.

  3. github-actions commented on Aug 12, 2025

    @github-actions
    Contributor

    👋 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.
  4. melvin-bot commented on Aug 12, 2025

    @melvin-bot

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

  5. melvin-bot commented on Aug 12, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  6. sobitneupane commented on Aug 12, 2025

    @sobitneupane
    Contributor

    Based on the newly implemented approach, we display the “New Message” button only when the New Message marker is not visible or is outside the viewport. Therefore, the button should not have been shown a second time. @FitseTLT, could you please follow up on this issue as well?

  7. FitseTLT commented on Aug 12, 2025

    @FitseTLT
    Contributor

    Based on the newly implemented approach, we display the “New Message” button only when the New Message marker is not visible or is outside the viewport. Therefore, the button should not have been shown a second time. @FitseTLT, could you please follow up on this issue as well?

    on it

  8. 17 remaining items

  9. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Sep 12, 2025
  10. changed the title [-]Chat - New message button appears and disappears when returning from thread for the second time[/-] [+][Due for payment 2025-09-19] Chat - New message button appears and disappears when returning from thread for the second time[/+] on Sep 12, 2025
  11. melvin-bot commented on Sep 12, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  12. melvin-bot commented on Sep 12, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.12-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2025-09-19. 🎊

    For reference, here are some details about the assignees on this issue:

    • @sobitneupane requires payment through NewDot Manual Requests
    • @FitseTLT requires payment (Needs manual offer from BZ)
  13. melvin-bot commented on Sep 12, 2025

    @melvin-bot

    @sobitneupane @sonialiap The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  14. sobitneupane commented on Sep 12, 2025

    @sobitneupane
    Contributor

    The payment will be handled in the parent issue. Good to close.

    cc: @sonialiap

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions