Skip to content

[Due for payment 2026-03-31] [Due for payment 2025-11-13] [Due for payment 2025-11-12] Start chat & Reports - From list does not load when there are more than 50 contacts #74239

Closed

Description

@mitarachim

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.2.44-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #71427
Email or phone of affected tester (no customers): applausetester+041102khd22@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Search

Action Performed:

Bug 1:

Precondition:

  • Log in with Expensifail account which has more than 50 contacts.
  1. Go to staging.new.expensify.com
  2. Open FAB > Start chat.
  3. Scroll to the bottom.

Bug 2:

Precondition:

  • Log in with Expensifail account which has more than 50 contacts.
  1. Go to staging.new.expensify.com
  2. Go to Reports > Expenses.
  3. Click Filters.
  4. Click From.
  5. Scroll to the bottom.

Expected Result:

Contact list will load.

Actual Result:

Contact list does not load.

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

Bug 1:

Bug6994272_1762292590102.bug_1.mp4

Bug 2:

Bug6994272_1762292590111.bug_2.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @NicMendonca

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Nov 4, 2025
  2. melvin-bot commented on Nov 4, 2025

    @melvin-bot

    Triggered auto assignment to @NicMendonca (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 Nov 4, 2025

    @melvin-bot

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

  4. melvin-bot commented on Nov 4, 2025

    @melvin-bot

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

  5. github-actions commented on Nov 4, 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. mitarachim commented on Nov 4, 2025

    @mitarachim
    Author

    Issue was found while executing QA for PR #71427

  7. mountiny commented on Nov 4, 2025

    @mountiny
    Contributor

    @mkzie2 @NikkiWines @sosek108 @ZhenjaHorbach Can you take a look please?

  8. 17 remaining items

  9. changed the title [-][Due for payment 2025-11-12] Start chat & Reports - From list does not load when there are more than 50 contacts[/-] [+][Due for payment 2025-11-13] [Due for payment 2025-11-12] Start chat & Reports - From list does not load when there are more than 50 contacts[/+] on Nov 6, 2025
  10. melvin-bot commented on Nov 6, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.45-6 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-11-13. 🎊

  11. melvin-bot commented on Nov 6, 2025

    @melvin-bot

    @dangrous @NicMendonca 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]

  12. melvin-bot commented on Mar 23, 2026

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

  13. jponikarchuk commented on Mar 23, 2026

    @jponikarchuk

    Deploy Blocker #86088 was identified to be related to the PR #75026 that attempted to fix this issue.

  14. melvin-bot commented on Mar 23, 2026

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

  15. melvin-bot commented on Mar 23, 2026

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

  16. jponikarchuk commented on Mar 23, 2026

    @jponikarchuk

    Deploy Blocker #86097 was identified to be related to the PR #75026 that attempted to fix this issue.

  17. changed the title [-][Due for payment 2025-11-13] [Due for payment 2025-11-12] Start chat & Reports - From list does not load when there are more than 50 contacts[/-] [+][Due for payment 2026-03-31] [Due for payment 2025-11-13] [Due for payment 2025-11-12] Start chat & Reports - From list does not load when there are more than 50 contacts[/+] on Mar 24, 2026
  18. melvin-bot commented on Mar 24, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.42-3 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 2026-03-31. 🎊

  19. melvin-bot commented on Mar 24, 2026

    @melvin-bot

    @dangrous 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]

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

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions