Skip to content

[HOLD for payment 2024-04-25] [$500] Chats are not loading in the LHN with Most Recent mode #39380

Closed

Description

@m-natarajan

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:
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers): @iwiznia
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @iwiznia
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1711986719647329

Action Performed:

  1. Open any app with most recent set

Expected Result:

LHN should be loaded with all the chats

Actual Result:

seeing just one chat in staging in my LHN but there should be a lot more chats in there

Workaround:

unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos

Add any screenshot/video evidence

image (1)

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01baee4a02953c567d
  • Upwork Job ID: 1777435508308942848
  • Last Price Increase: 2024-04-08

Activity

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

    @melvin-bot

    Triggered auto assignment to @CortneyOfstad (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  3. melvin-bot commented on Apr 1, 2024

    @melvin-bot

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

  4. MelvinBot commented on Apr 1, 2024

    @MelvinBot
    Contributor

    This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

  5. github-actions commented on Apr 1, 2024

    @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. marcaaron commented on Apr 1, 2024

    @marcaaron
    Contributor

    @hayata-suenaga can you try to check logs for @iwiznia and see if anything is happening?

    This might not need to be an App deploy blocker and could be a Web deploy issue.

    Sounds like a backend issue. What do you think?

    Looks like there's more context in this thread: https://expensify.slack.com/archives/C049HHMV9SM/p1711986719647329

  7. hayata-suenaga commented on Apr 1, 2024

    @hayata-suenaga
    Contributor

    Might be from OpenApp.

    Checking this log right now

  8. 24 remaining items

  9. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Apr 12, 2024
  10. changed the title [-][$500] Chats are not loading in the LHN with `Most Recent` mode[/-] [+][HOLD for payment 2024-04-25] [$500] Chats are not loading in the LHN with `Most Recent` mode[/+] on Apr 18, 2024
  11. melvin-bot commented on Apr 18, 2024

    @melvin-bot

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

  12. melvin-bot commented on Apr 18, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.62-17 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 2024-04-25. 🎊

  13. melvin-bot commented on Apr 18, 2024

    @melvin-bot

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@hayata-suenaga] The PR that introduced the bug has been identified. Link to the PR:
    • [@hayata-suenaga] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
    • [@hayata-suenaga] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
    • [@hayata-suenaga] Determine if we should create a regression test for this bug.
    • [@hayata-suenaga] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
    • [@CortneyOfstad] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  14. mvtglobally commented on Apr 18, 2024

    @mvtglobally

    Issue not reproducible during KI retests. (First week)

  15. hayata-suenaga commented on Apr 18, 2024

    @hayata-suenaga
    Contributor

    The issue was fixed in this PR. I'm going to write a PM soon. Closing this issue

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.EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributorsNeeds ReproductionReproducible steps neededWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions