Skip to content

LHN - New member's workspace chat is not displayed in LHN #73469

Closed

Description

@lanitochka17

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.38-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: #73074
Email or phone of affected tester (no customers): gocemate+b2154745@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

  1. Open the app
  2. Open 1:1 DM with non-existing user (random email)
  3. Click + > Track distance > Manual
  4. Enter amount > Next
  5. On confirm page, click Rate
  6. Click Upgrade > Got it, thanks
  7. Click RHP back button to return to confirm page
  8. Click Create expense
  9. Observe LHN

Expected Result:

New member's workspace chat should be displayed on LHN

Actual Result:

New member's workspace chat is not displayed in LHN

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop
Platforms Tested: On which of our officially supported platforms was this issue tested:
  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug6983633_1761339178050.Recording__6328.mp4

View all open jobs on GitHub

Activity

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

    @melvin-bot

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

  3. melvin-bot commented on Oct 24, 2025

    @melvin-bot

    Triggered auto assignment to @sonialiap (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.

  4. melvin-bot commented on Oct 24, 2025

    @melvin-bot

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

  5. github-actions commented on Oct 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. arosiclair commented on Oct 27, 2025

    @arosiclair
    Contributor

    Reproduced in staging v9.2.38-1 and not in prod v9.2.37-8

  7. situchan commented on Oct 27, 2025

    @situchan
    Contributor

    This is now expected behavior. Asked QA team to retest #73074

  8. arosiclair commented on Oct 27, 2025

    @arosiclair
    Contributor

    I'm not sure how this flow is supposed to work.

    On prod, the distance rate upgrade creates a workspace that belongs to the recipient and the submitter is just a member. In that case, I think it's a bug that you can see the recipient's workspace chat. When you click on it, it actually disappears from the LHN.

    On staging, the upgrade creates a workspace that belongs to the submitter and the recipient is not a member. So it's not surprising there is no workspace chat for the recipient.

  9. arosiclair commented on Oct 27, 2025

    @arosiclair
    Contributor

    Okay, based on the design doc, this is the correct behavior

    If the user entered someone else’s email address in the “To” field, then once they click the upgrade button, we’ll create a new workspace for them, automatically enable the “Distance Rate” feature, and also invite the other user to be an admin on the workspace.

    We actually already have another blocker to fix that here.

    So based on that, I would not expect the other member's workspace chat to be visible and this isn't a bug.

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions