Skip to content

Chat - No New message green line when receive new message #59357

Closed

Description

@IuliiaHerets

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: v9.1.21-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: https://expensify.testrail.io/index.php?/tests/view/5834574&group_by=cases:section_id&group_order=asc&group_id=296775
Email or phone of affected tester (no customers): applausetester+gm103457@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Lenovo 80ES / Windows 10 Pro
App Component: Chat Report View

Action Performed:

Precondition:
Account A and Account B have previous conversation

  1. Account A sends a message to Account B
  2. Account B opens the chat

Expected Result:

There should be green line for new message

Actual Result:

There is no green line for new message when user opens the chat with unread message

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6787907_1743425270046.Recording__5307.mp4

View all open jobs on GitHub

Activity

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

    @melvin-bot

    Triggered auto assignment to @flaviadefaria (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. melvin-bot commented on Mar 31, 2025

    @melvin-bot

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

  4. melvin-bot commented on Mar 31, 2025

    @melvin-bot

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

  5. github-actions commented on Mar 31, 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.
  6. flaviadefaria commented on Mar 31, 2025

    @flaviadefaria
    Contributor

    I was able to recreate the issue.

  7. melvin-bot commented on Mar 31, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  8. Julesssss commented on Mar 31, 2025

    @Julesssss
    Contributor

    Oh interesting. It's the inverse of this issue where the green line is showing for your own messages.

  9. 4 remaining items

  10. lanitochka17 commented on Apr 3, 2025

    @lanitochka17

    Another tester was able to reproduce this issue.

    Recording.3.mp4
  11. grgia commented on Apr 4, 2025

    @grgia
    Contributor

    @lanitochka17 is this on prod?

  12. lanitochka17 commented on Apr 4, 2025

    @lanitochka17

    @grgia yes

  13. Julesssss commented on Apr 4, 2025

    @Julesssss
    Contributor

    Hi @lanitochka17, is this issue also occuring now? I haven't been able to reproduce my linked issue

  14. lanitochka17 commented on Apr 10, 2025

    @lanitochka17

    Hi @Julesssss This #59393 is not reproducible now.

    0-02-01-6837c69866665c666dad24d44d2387e0141d53e0d8731ce8475098cb2affa756_4b3b1b1739e28d74.mp4
  15. flaviadefaria commented on Apr 28, 2025

    @flaviadefaria
    Contributor

    Looks like we're good to close this then. Please reopen in case I missed anything.

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions