Skip to content

Concierge - Welcome screen opens instead of chat history when opening main chat via header #105423

Open

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): noidjsoiisjd@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Other

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to Concierge.
  3. Click Hide chat history if welcome screen is not shown.
  4. Send a message to Concierge.
  5. Click on the header subtitle link.
    → Chat history opens.
  6. Create a task by sending [] task.
  7. Go to Spend > Expenses.
  8. Click Filters > Type > Task.
  9. Open the task.
  10. Click New chat.
  11. Send a message to Concierge.
  12. Click on the header subtitle link.
    → Welcome screen opens instead of chat history.

Expected Result:

In Step 12, when navigating to main chat via header subtitle, chat history will open (consistent with Step 5).

Actual Result:

In Step 12, when navigating to main chat via header subtitle, welcome screen opens instead of chat history.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7300004_1793308879471.2.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7300004

Issue OwnerCurrent Issue Owner: @rushatgabhane

Activity

  1. applause-bot commented on Oct 29, 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/e1837f869ec355482902c7fbcc4ae50592341bd3e6ef139f931440f4642d6508

  2. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 29, 2026
  3. melvin-bot commented on Oct 29, 2026

    @melvin-bot

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

  4. melvin-bot commented on Oct 29, 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 29, 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 29, 2026

    @melvin-bot

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

  7. github-actions commented on Oct 29, 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 29, 2026

    @rushatgabhane
    Member

    definitely not a blocker

  9. MelvinBot commented on Oct 29, 2026

    @MelvinBot
    Contributor

    Deploy Blocker Investigation

    Causing PR: [Payment due @mkhutornyi] Add ask Concierge screen (high confidence)

    Recommendation: Demote and fix forward. Don't revert. This bug only happens in one narrow flow, and nothing is lost. The user can tap "View chat history" to see the history. Reverting a 58-file feature that removes a beta and depends on a backend change is riskier than the bug.

    Root cause: That PR shows chat history only when showFullHistory is on or the Concierge route has a reportActionID param (useConciergeAskState.ts:60-61). In the Search panel flow, the subtitle click goes back without setting that param, so the welcome screen shows.

    Suggested fix: In the duplicate-skipping branch of ParentNavigationSubtitle.tsx:189-199, set reportActionID on the previous route before calling Navigation.goBack(). The Inbox branch already does this at L250-L259.

    Investigation details

    Steps 1–5 (Inbox) work. The new thread opens in the Inbox stack. The subtitle click takes the branch at ParentNavigationSubtitle.tsx:250-259. That branch sets reportActionID on the Concierge screen, then goes back, so history expands.

    Steps 6–12 (Search panel) fail:

    1. The task opens in a Search panel. Its parent is Concierge, so the header shows New chat.
    2. New chat collapses history and opens Concierge with no reportActionID (HeaderView.tsx:330-333). It opens in the same panel (getReportRouteForCurrentContext.ts:19-21).
    3. Sending a message opens the thread in that panel. The panel now holds task → Concierge → thread.
    4. The subtitle click hits the branch that skips duplicate screens (ParentNavigationSubtitle.tsx:189-199). Because the previous screen is already Concierge, it calls Navigation.goBack() without setting reportActionID.
    5. Concierge now has no reportActionID, and showFullHistory is off, so shouldShowWelcome is true.

    That branch existed before the PR, and the PR doesn't change it. Dropping the param was harmless until the PR made the param decide whether history shows.

    Fix sketch:

    if ((previousRoute?.name === SCREENS.RIGHT_MODAL.SEARCH_REPORT || previousRoute?.name === SCREENS.RIGHT_MODAL.EXPENSE_REPORT) &&
        previousRoute.params && 'reportID' in previousRoute.params && previousRoute.params.reportID === parentReportID) {
        if (isVisibleAction && parentReportActionID && previousRoute.key && currentFocusedNavigator?.state?.key) {
            Navigation.setParams({reportActionID: parentReportActionID}, previousRoute.key, currentFocusedNavigator.state.key);
        }
        Navigation.goBack();
        return;
    }

    This also fixes jumping to the parent message for any parent opened in a Search panel. A narrower option is to change only the Concierge code, for example by expanding history when you return to Concierge from one of its threads.

    Caveat: I found this path by reading the code. I didn't reproduce it in the app.


    view run

  10. mkhutornyi commented on Oct 30, 2026

    @mkhutornyi
    Contributor

    I think we agreed in PR that RHP will be handled separately in another PR.

    Btw staging testers are more thorough than PR build testers? We were expecting all these "bugs" to be reported earlier in adhoc build.

  11. puneetlath commented on Oct 30, 2026

    @puneetlath
    Contributor

    Demoting.

  12. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Oct 30, 2026
  13. added
    ReviewingHas a PR in review
    and removed on Nov 2, 2026
  14. jeffrey-graham commented on Nov 7, 2026

    @jeffrey-graham
  15. melvin-bot commented on Nov 7, 2026

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

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions