Skip to content

[Due for payment 2026-11-11] [$175] Concierge - User lands on chat twice after being navigated to thread and returning to chat. #105443

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: 9.5.26-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: #100552
Email or phone of affected tester (no customers): ibellicotest+3215@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app)
App Component: Other

Action Performed:

Prerequisite: Select "Track expenses for my business" during onboarding.

  1. Open the Expensify app.
  2. Navigate to Concierge chat.
  3. Tap on "Hide chat history"
  4. Ask a question and send it.
  5. Once you land on thread, tap on back button on the top left corner.
  6. After returning to chat, tap on back button again.
  7. Note that you land on chat again.

Expected Result:

After tapping on back button after returning from a thread, user should land on "Inbox"

Actual Result:

Back button leads to Concierge chat one more time, after returning to chat from a thread that was created from welcome screen.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7300113_1793320753512.AI_14.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Chandana Kiran
Bug ID: 7300113

Upwork Automation - Do Not Edit
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 Oct 30, 2026
  2. applause-bot commented on Oct 30, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/655518949f832e3523032b9e5268fed6b7c8b1a46d44c36f88faf0f8341eca31

  3. melvin-bot commented on Oct 30, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #100552

  4. melvin-bot commented on Oct 30, 2026

    @melvin-bot

    @puneetlath @mkhutornyi you have been assigned to this deploy blocker because you reviewed the offending PR: #100552

  5. melvin-bot commented on Oct 30, 2026

    @melvin-bot

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

  6. melvin-bot commented on Oct 30, 2026

    @melvin-bot

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

  7. github-actions commented on Oct 30, 2026

    @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.
  8. rushatgabhane commented on Oct 30, 2026

    @rushatgabhane
    Member

    @MelvinBot how to fix this

  9. 27 remaining items

  10. mkhutornyi commented on Nov 9, 2026

    @mkhutornyi
    Contributor

    This is not a regression from #100552. The real offending PR was #90072.
    Evidence that this was production bug: #105443 (comment), #105443 (comment), #105443 (comment)

    I was assigned in project on Aug 10 (before Sep 19).

  11. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Nov 10, 2026
  12. melvin-bot commented on Nov 10, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  13. melvin-bot commented on Nov 10, 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
  14. mallenexpensify commented on Nov 13, 2026

    @mallenexpensify
    Contributor

    Claude posting on behalf of Matt:

    Your call. Job price: $175 (standard, no Help Wanted, assigned 2026-10-30).

    • mkhutornyi (C+): 100% if not a regression, 0% if it is, via NewDot
    • rushatgabhane (Backend Contributor): no payment

    The BrowserStack field names #100552, which mkhutornyi approved. It merged 2026-10-29. This issue was created 2026-10-30, inside the regression window.

    mkhutornyi says the cause was #90072, in production since 2026-05-13, outside the window, and asks for the $250 project price: comment

    Next: decide on the regression and the price. Then press Caps+Y and pay.

    Evidence
    • C+ checklist, with test steps: comment
    • TestRail case: none yet
    • Resolving PR: #105565 by MelvinBot, merged 2026-11-02, approved by mkhutornyi, puneetlath. No revert.
    • Offending PR (BrowserStack field): #100552 by rushatgabhane, approved by mkhutornyi, puneetlath. Merged 2026-10-29. No production deploy found.
    • Cause per mkhutornyi: #90072 by chrispader, approved by rlinoz. No payee is on it.
    • rushatgabhane says the bug also happens in production: comment
    • Test videos: C+ 2/5.

    PAYPREP v1

  15. mallenexpensify commented on Nov 15, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @mkhutornyi due $250 via NewDot

    Paying $250 cuz project is still open, if it were close, pay would be current standard amount.

  16. trjExpensify commented on Nov 20, 2026

    @trjExpensify
    Contributor

    approved $250 for @mkhutornyi

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