Skip to content

Chat - Green line does not appear when receiving a new message, but appears in the chat when sending a message #6424

Closed

Description

@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. Go to https://staging.new.expensify.com
  2. Log in with any account
  3. Send some messages to Account A
  4. Enter the conversation that has unread messages and verify there is a green line indicating the New Messages.
  5. Answer to user.

Expected Result:

Verify there is a green line indicating the New Messages

Actual Result:

When I receive a message the green line is not displayed but when I answer it appears.
Conversation is starting from tip instead of bottom

Workaround:

Unknown

Platform:

Where is this issue occurring?

  • Web
  • iOS
  • Android
  • Desktop App
  • Mobile Web

Version Number: 1.1.16-1

Reproducible in staging?: Yes

Reproducible in production?: No

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos:

Bug5342011_Recording__210.mp4

Expensify/Expensify Issue URL:
Issue reported by: Applause
Slack conversation:

View all open jobs on GitHub

Activity

  1. OSBotify commented on Nov 23, 2021

    @OSBotify
    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.
  2. MelvinBot commented on Nov 23, 2021

    @MelvinBot
    Contributor

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

  3. johnmlee101 commented on Nov 23, 2021

    @johnmlee101
    Contributor

    Currently eyeing #6248 as a culprit but double checking

  4. johnmlee101 commented on Nov 23, 2021

    @johnmlee101
    Contributor

    Okay tested the revert locally and it fixes the regression. Assigning @parasharrajat for the time being as he's taking a look!

  5. MelvinBot commented on Nov 23, 2021

    @MelvinBot
    Contributor

    📣 @parasharrajat You have been assigned to this job by @johnmlee101!
    Please apply to this job in Upwork and let us know when we can expect a PR to be ready for review 🧑‍💻
    Keep in mind: Code of Conduct | Contributing 📖

  6. chiragsalian commented on Nov 24, 2021

    @chiragsalian
    Contributor

    @kavimuru, the fix for this has been CP-d. Can you retest and then close the issue if its resolved.

  7. isagoico commented on Nov 25, 2021

    @isagoico

    Retest for this was a pass! Closing!

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

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions