Skip to content

[$250] Expense - Recipient list auto scrolls down to reveal only "Contacts" after clearing search field #55715

Description

@vincdargento

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.0.89-2
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): applausetester+100106kh@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.0 / Chrome
App Component: Other

Action Performed:

Precondition:

  • Account has many contacts (Expensifail account).
  • There are a few contacts under Recent section in contact list (create chat with a few users to have some contacts under Recent section).
  1. Go to staging.new.expensify.com
  2. Open FAB > Create expense > Manual.
  3. Enter amount > Next.
  4. Type search term that will return a few members in the search result.
  5. Clear the search field.

Expected Result:

The recipient list will not scroll down after clearing the search field.

Actual Result:

The recipient list auto scrolls down to reveal only "Contacts" after clearing the search field.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

bug.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021882867353031260828
  • Upwork Job ID: 1882867353031260828
  • Last Price Increase: 2025-02-07
Issue OwnerCurrent Issue Owner: @Pujan92

Activity

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

    @melvin-bot

    Triggered auto assignment to @laurenreidexpensify (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 Jan 24, 2025

    @melvin-bot

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

  4. melvin-bot commented on Jan 24, 2025

    @melvin-bot

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

  5. github-actions commented on Jan 24, 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. vincdargento commented on Jan 24, 2025

    @vincdargento
    Author

    @laurenreidexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

  7. srikarparsi commented on Jan 24, 2025

    @srikarparsi
    Contributor

    Adding the external label

  8. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Jan 24, 2025
  9. 19 remaining items

  10. melvin-bot commented on Jan 31, 2025

    @melvin-bot

    @Pujan92, @srikarparsi, @laurenreidexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  11. melvin-bot commented on Jan 31, 2025

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  12. laurenreidexpensify commented on Feb 3, 2025

    @laurenreidexpensify
    Contributor

    Let's wait for some more proposals to come in

  13. melvin-bot commented on Feb 4, 2025

    @melvin-bot

    @Pujan92, @srikarparsi, @laurenreidexpensify Still overdue 6 days?! Let's take care of this!

  14. melvin-bot commented on Feb 6, 2025

    @melvin-bot

    @Pujan92, @srikarparsi, @laurenreidexpensify 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!

  15. laurenreidexpensify commented on Feb 6, 2025

    @laurenreidexpensify
    Contributor

    Still waiting on proposals here

  16. melvin-bot commented on Feb 7, 2025

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  17. mvtglobally commented on Feb 8, 2025

    @mvtglobally

    Issue not reproducible during KI retests. (First week)

  18. melvin-bot commented on Feb 10, 2025

    @melvin-bot

    @Pujan92, @srikarparsi, @laurenreidexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

  19. laurenreidexpensify commented on Feb 10, 2025

    @laurenreidexpensify
    Contributor

    Closing as not reproducible in KI testing

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

Metadata

Metadata

Labels

DailyKSv2ExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributors

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions