Skip to content

[Due for payment 2025-10-22] Workspace - Missing contact when inviting member #72516

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.30-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: #71455
Email or phone of affected tester (no customers): sdonjsdoijsiojs@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Workspace Settings

Action Performed:

Bug 1:

  1. Go to staging.new.expensify.com
  2. Log in with Gmail account.
  3. Open 1:1 DM with new user.
  4. Send a message.
  5. Create a workspace.
  6. Go to workspace settings > Overview.
  7. Click More > Invite.

Bug 2:

  1. Go to staging.new.expensify.com
  2. Log in with Expensifail account (account has many contacts in the same domain).
  3. Go to workspace settings > Overview.
  4. Click More > Invite.
  5. Scroll down the list.

Expected Result:

Bug 1: The DM user will appear in the contact list.
Bug 2: The list will load more contacts when scrolled down.

Actual Result:

Bug 1: The DM user does not appear in the contact list.
Bug 2: The list does not load more contacts when scrolled down.

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

Bug6974021_1760397369720.Bug_1.mp4

Bug 2

Bug6974021_1760397369722.Bug_2.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @bfitzexpensify

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 Oct 13, 2025
  2. melvin-bot commented on Oct 13, 2025

    @melvin-bot

    Triggered auto assignment to @bfitzexpensify (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 Oct 13, 2025

    @melvin-bot

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

  4. github-actions commented on Oct 13, 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.
  5. melvin-bot commented on Oct 13, 2025

    @melvin-bot

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

  6. lakchote commented on Oct 14, 2025

    @lakchote
    Contributor
  7. nkdengineer commented on Oct 14, 2025

    @nkdengineer
    Contributor

    @lakchote Please assign me and @allroundexperts to this issue then i can open the follow up PR

  8. 21 remaining items

  9. melvin-bot commented on Oct 22, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@bfitzexpensify)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  10. bfitzexpensify commented on Oct 23, 2025

    @bfitzexpensify
    Contributor

    @allroundexperts please complete the BZ checklist

    @nkdengineer offer sent via Upwork

  11. nkdengineer commented on Oct 23, 2025

    @nkdengineer
    Contributor

    @bfitzexpensify It's my regression

  12. bfitzexpensify commented on Oct 23, 2025

    @bfitzexpensify
    Contributor

    Ah, thanks for letting me know

  13. allroundexperts commented on Oct 26, 2025

    @allroundexperts
    Contributor

    We can close this @bfitzexpensify

  14. trjExpensify commented on Jan 5, 2026

    @trjExpensify
    Contributor

    👋 @bfitzexpensify @allroundexperts this was a regression from a PR attached to another issue, so confirming no payments were supposed to be due or paid here? CC: @mallenexpensify.

  15. bfitzexpensify commented on Jan 7, 2026

    @bfitzexpensify
    Contributor

    Correct

  16. trjExpensify commented on Jan 7, 2026

    @trjExpensify
    Contributor

    Thanks, Ben. I'lll reject this one.

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.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions