Skip to content

Chat - LHN displayed as "comment deleted" for the new user when initiating chat and navigating to LHN  #6426

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. Launch the app and login.
  2. Click on New Chat
  3. Search for a user that you don't have any messages with and open the chat.

Expected Result:

When you navigate from the chat that doesn't have a message, it disappears from the left hand navigation.

Actual Result:

When you navigate from the chat that doesn't have a message, it appears at the LHN with "comment deleted" for that user

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:
Bug5341986_23 11-new_message-1

Bug5341986_23.11-new_message-2.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 @thienlnam (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  3. thienlnam commented on Nov 23, 2021

    @thienlnam
    Contributor

    Looks like this is from #4133

    cc @chiragsalian

  4. chiragsalian commented on Nov 24, 2021

    @chiragsalian
    Contributor

    Oh i missed this, assigning to self as i investigate.

  5. self-assigned this
    on Nov 24, 2021
  6. parasharrajat commented on Nov 24, 2021

    @parasharrajat
    Member

    @chiragsalian I think it was discussed here #3293 (comment) and fixed here #6458

  7. chiragsalian commented on Nov 24, 2021

    @chiragsalian
    Contributor

    oh nice, thanks for that @parasharrajat 🙇
    Looks like that PR resolves this issue. I'll link it here and ensure it get's CP-d.

  8. chiragsalian commented on Nov 24, 2021

    @chiragsalian
    Contributor

    @kavimuru the fix has been CP-d. Can you retest and close issue when you get the chance.

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