You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Concierge - Welcome screen opens instead of chat history when opening main chat via header #105423
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:
Go to staging.new.expensify.com
Go to Concierge.
Click Hide chat history if welcome screen is not shown.
Send a message to Concierge.
Click on the header subtitle link.
→ Chat history opens.
Create a task by sending [] task.
Go to Spend > Expenses.
Click Filters > Type > Task.
Open the task.
Click New chat.
Send a message to Concierge.
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.
👋 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:
Identify the pull request that introduced this issue and revert it.
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:
The task opens in a Search panel. Its parent is Concierge, so the header shows New chat.
Sending a message opens the thread in that panel. The panel now holds task → Concierge → thread.
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.
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.
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.
Activity
applause-bot commentedon Oct 29, 2026
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
melvin-bot commentedon Oct 29, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #100552
melvin-bot commentedon Oct 29, 2026
@puneetlath @mkhutornyi you have been assigned to this deploy blocker because you reviewed the offending PR: #100552
melvin-bot commentedon Oct 29, 2026
@rushatgabhane you have been assigned to this deploy blocker because you authored the offending PR: #100552
melvin-bot commentedon Oct 29, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Oct 29, 2026
👋 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:
rushatgabhane commentedon Oct 29, 2026
definitely not a blocker
MelvinBot commentedon Oct 29, 2026
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
showFullHistoryis on or the Concierge route has areportActionIDparam (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
reportActionIDon the previous route before callingNavigation.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
reportActionIDon the Concierge screen, then goes back, so history expands.Steps 6–12 (Search panel) fail:
reportActionID(HeaderView.tsx:330-333). It opens in the same panel (getReportRouteForCurrentContext.ts:19-21).Navigation.goBack()without settingreportActionID.reportActionID, andshowFullHistoryis off, soshouldShowWelcomeis 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:
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
mkhutornyi commentedon Oct 30, 2026
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.
puneetlath commentedon Oct 30, 2026
Demoting.
jeffrey-graham commentedon Nov 7, 2026
melvin-bot commentedon Nov 7, 2026