Skip to content

Chat history is shown and it changes to welcome screen after navigating via header subtitle #105506

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

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. Open search router.
  5. Type anything.
  6. Click Ask Concierge.
  7. Click on the blue Thread in RHP.
  8. Type anything and send it in the main chat.
  9. Click Concierge on the header subtitle.

Expected Result:

Chat history will remain shown after navigating to Concierge via header subtitle.

Actual Result:

Chat history is shown and then it changes to welcome screen after navigating to Concierge via header subtitle.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7300732_1793374008321.5.1.mp4

View all open jobs on GitHub

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

Issue OwnerCurrent Issue Owner: @rushatgabhane

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/f823f59076051a3a1590a901856d1a5b6d318944e5bfea6b4756a1e49948dfec

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

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

  7. melvin-bot commented on Oct 30, 2026

    @melvin-bot

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

  8. MelvinBot commented on Oct 30, 2026

    @MelvinBot
    Contributor

    Deploy Blocker Analysis

    Causing PR: [Payment due @mkhutornyi] Add ask Concierge screen. Confidence is high for the PR and medium for the exact timing path. I did not reproduce this in a browser.

    Root cause: The new Concierge screen shows chat history only while the reportActionID route param is set. It does not save that state anywhere else (useConciergeAskState.ts:60-61). Existing scroll-anchoring code clears that param. When it does, isHistoryCollapsedByUser is still true from step 3, so the welcome screen comes back.

    Recommendation: Demote and fix in a follow-up. A revert is too large for this bug. The PR changes about 60 files and depends on a backend change. The bug needs a specific 9-step path, loses no data, and "View chat history" brings the history back. If you want it fixed before deploy, the fix is about 5 lines (below).

    How the bug happens
    1. Step 7: The "Thread" link opens the Concierge chat at a linked message, so reportActionID is set and history shows.
    2. Step 8: Sending a message (useComposerSubmit.ts) makes useReportActionsNewActionLiveTail.ts:108-127 jump to the latest messages. Once that load finishes, it clears the param (lines 176-197). The app then navigates to the new thread, and the Concierge screen freezes underneath it before that effect runs.
    3. Step 9: ParentNavigationSubtitle.tsx:249-259 sets the param again and goes back. The first frame shows history. Then the waiting effect runs, clears the param, and the welcome screen appears.

    Other code that clears the param would cause the same flip, for example LinkedActionNotFoundGuard and ReportRouteParamHandler.

    None of the other 36 PRs in the Deploy Checklist: New Expensify 2026-10-29 change the Concierge welcome or history state.

    Suggested fix

    When the Concierge chat opens at a linked message, keep history expanded in context state. Add this next to the existing effect in ReportActionsSkeletonGuard.tsx:46-54:

    const {reportActionIDFromRoute} = readinessSignals;
    useEffect(() => {
        if (!reportActionIDFromRoute || !state.isConciergeHistoryExpanded) {
            return;
        }
        setConciergeShowFullHistory(true);
    }, [reportActionIDFromRoute, state.isConciergeHistoryExpanded, setConciergeShowFullHistory]);

    "Hide chat history" still works, because collapseHistory() sets the state to false and clears the param in one step.


    Next Steps: Reply with @MelvinBot implement this to create a draft PR, or @MelvinBot <your feedback> to refine this analysis.


    view run

  9. 5 remaining items

  10. melvin-bot commented on Nov 3, 2026

    @melvin-bot

    @rushatgabhane Whoops! This issue is 2 days overdue. Let's get this updated quick!

  11. melvin-bot commented on Nov 3, 2026

    @melvin-bot

    @rushatgabhane Whoops! This issue is 2 days overdue. Let's get this updated quick!

  12. melvin-bot commented on Nov 3, 2026

    @melvin-bot

    @rushatgabhane Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  13. melvin-bot commented on Nov 5, 2026

    @melvin-bot

    @rushatgabhane Huh... This is 4 days overdue. Who can take care of this?

  14. melvin-bot commented on Nov 5, 2026

    @melvin-bot

    @rushatgabhane Huh... This is 4 days overdue. Who can take care of this?

  15. melvin-bot commented on Nov 5, 2026

    @melvin-bot

    @rushatgabhane Eep! 4 days overdue now. Issues have feelings too...

  16. melvin-bot commented on Nov 6, 2026

    @melvin-bot

    @rushatgabhane 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

  17. melvin-bot commented on Nov 10, 2026

    @melvin-bot

    @rushatgabhane 10 days overdue. I'm getting more depressed than Marvin.

  18. melvin-bot commented on Nov 12, 2026

    @melvin-bot

    @rushatgabhane 12 days overdue. Walking. Toward. The. Light...

  19. melvin-bot commented on Nov 13, 2026

    @melvin-bot

    @puneetlath @rushatgabhane @mkhutornyi this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

  20. expensify-chore-bot commented on Nov 17, 2026

    @expensify-chore-bot

    This issue has not been updated in over 14 days. @puneetlath, @rushatgabhane, @mkhutornyi eroding to Weekly issue.

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

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions