Skip to content

[Due for payment 2026-09-15] LHN - Removed user can access Concierge address flow and archived chat is unresponsive from LHN #99731

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: V9.4.63-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #94316
Email or phone of affected tester (no customers): Applausetesterjsjid@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Redmi note 10s android 13
App Component: User Settings

Action Performed:

Pre-condition: user B Gmail invalidated account

  1. Launch app
  2. Login Expensifail account
  3. Create workspace with address
  4. Enable distance rate and from settings - exclude commutes select office and home location
  5. Invite a member ( user B)
  6. Remove user B
  7. Login as user B
  8. From search open archived chat
  9. Tap address and complete the flow
  10. Go to LHN
  11. Tap on archived chat
  12. Note archived chat is not responding on tapping
  13. Open archived chat from search
  14. Note archived chat can be opened from search

Expected Result:

After removing user, concierge add address button must not be shown.

Archived chat should respond and open when tapped from the LHN, consistent with opening it from Search.

Actual Result:

After removing user also, concierge add address button is shown.

Archived chat is unresponsive when opened from LHN.

Note : Time sensitive add home address element is disappeared after removing user but in archived chat add address element is present.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7244868_1787894098306.Screenrecorder-2026-08-28-10-10-46-570.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7244868

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

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

    @melvin-bot

    @Gonals recently merged #94316, but they are OOO right now, so I'll auto-assign someone else.

  3. melvin-bot commented on Aug 28, 2026

    @melvin-bot

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

  4. melvin-bot commented on Aug 28, 2026

    @melvin-bot

    @robertjchen @JmillsExpensify @fedirjh you have been assigned to this deploy blocker because you reviewed the offending PR: #94316

  5. melvin-bot commented on Aug 28, 2026

    @melvin-bot

    @Gonals you have been assigned to this deploy blocker because you authored the offending PR: #94316

  6. melvin-bot commented on Aug 28, 2026

    @melvin-bot

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

  7. 36 remaining items

  8. FitseTLT commented on Sep 9, 2026

    @FitseTLT
    Contributor

    BugZero Checklist:

    • [Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to the comment on the PR: N/A — see note below
      Link to the comment on the Issue: N/A — see note below

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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: N/A — not critical. The Deploy Blocker label was removed and the report-only-from-Search workaround kept the flow reachable throughout.

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue: https://github.com/Expensify/Expensify/issues/682496

    Regression Test Proposal

    Precondition:

    • An Expensifail account, and a second account (User B) on a mobile device (Android or iOS).
    • A workspace with an address configured, distance rates enabled, and Exclude commutes set to office and home locations.
    • User B has been invited to that workspace and then removed, so their workspace chat is archived.

    Test:

    1. On Android or iOS, log in as User B.
    2. From Search, open the archived workspace chat.
    3. Tap the address prompt and open the Settings RHP.
    4. Return to the LHN by tapping the Inbox tab.
    5. Tap the archived chat row in the LHN.
    6. Verify the archived chat opens and the row is responsive.
    7. Verify the archived chat can still be opened from Search.
    8. Verify tapping different LHN rows opens the corresponding reports.

    Do we agree 👍 or 👎

    Zapier Logs Run ID: 00040eee-d669-a0b9-3110-5c24170f8794
  9. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Sep 9, 2026
  10. melvin-bot commented on Sep 14, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  11. melvin-bot commented on Sep 14, 2026

    @melvin-bot

    Payment Summary

    Resolving PRs:

    BugZero Checklist (@mallenexpensify)

    • I have confirmed assignees, roles, and Upwork contracts look correct
    • I have paid out Upwork contracts / manual NewDot requests
    • [BugZero Assignee] I have created a GH issue for creating/updating the regression test once above steps have been agreed upon
  12. mallenexpensify commented on Sep 16, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @FitseTLT due $250 via NewDot

    @FitseTLT in the future, will you please comment on all mentions of 'deploy blockers', even if you were part of the offending PR? Otherwise I have to dig around to confirm if you were assigned or not. Thx

  13. flaviadefaria commented on Sep 22, 2026

    @flaviadefaria
    Contributor

    Approved: @FitseTLT due $250 via NewDot

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

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions