The + button in the Ask Concierge anything field on the Home tab does not perform any action.

[m-natarajan]

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

---

Version Number:
Reproducible in staging?: Needs Reproduction (Unable to reproduce)
Reproducible in production?: Needs Reproduction
If this was caught during regression testing, add the test name, ID and link from BrowserStack:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @AndrewGable
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

1. Sign out and sign back in to the account.
2. Navigate to the Home tab.
3. Locate the Ask Concierge anything field.
4. Tap the + button.
5. Observe the result.

Expected Result:

Tapping the + button should perform the expected action, such as opening the add attachment/action options.

Actual Result:

Tapping the + button does nothing.

Note:

The issue can be reliably reproduced after signing out and back in, likely when the user does not have any existing messages with Concierge and the chat has not yet been created.

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Screenshots/Videos

Screen_Recording_20260826_112341_Expensify.Dev-2.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @Ollyws

[MelvinBot]

Proposal

What is the root cause of that problem?

The + button (and the Send button) in the Home tab's "Ask Concierge anything" composer are gated on shouldShowAskConcierge, which is only true once the Concierge report already exists in Onyx:

shouldShowAskConcierge = !!targetReportID && !!targetReport

useAskConcierge.tsx:30

CONCIERGE_REPORT_ID is server-driven — it is only populated by the OpenApp / ReconnectApp response, never written by a client action. So right after signing out and back in (and permanently on accounts that have never opened Concierge), there is a window where CONCIERGE_REPORT_ID — or its REPORT collection record — is absent. During that window shouldShowAskConcierge is false, so the + button is rendered disabled and tapping it does nothing (ConciergePromptBox.tsx:162).

The composer is effectively inert in this state — you can type, but Send stays disabled too (ConciergePromptBox.tsx:114), and both askConcierge helpers early-return before ever calling openConciergeAnywhere. That means the composer can never reach navigateToConciergeChat's lazy report-creation path (Report/index.ts:4245) — there is no way to bootstrap the Concierge report from this surface.

What changes do you think we should make in order to solve the problem?

Stop hard-disabling the composer controls on !shouldShowAskConcierge. Instead, keep the + button and Send enabled and let the tap/send bootstrap the Concierge report when it doesn't exist yet:

• The interaction should route through openConciergeAnywhere → navigateToConciergeChat, which already lazily creates the report via navigateToAndOpenReport({userLogins: [CONST.EMAIL.CONCIERGE]}) when conciergeReportID is empty.
• Remove the early-return-before-openConciergeAnywhere in useAskConcierge so the create path is actually reachable, and gate only on !!targetReportID (not !!targetReport) for the enabled state.
• Web needs its own creation fallback: on web, useOpenConciergeAnywhere/index.tsx only opens the side panel and has no report-creation path, so it relies on the report already existing.

What alternative solutions did you explore? (Optional)

Proactively create/fetch the Concierge report on the Home tab mount (or immediately after OpenApp) so the report is always present by the time the composer renders. This avoids the empty-state entirely but is broader than the surface where the bug appears.

Verification (web) & investigation details

Live web check (existing account, Concierge report present): the composer works as expected — this is exactly the state where shouldShowAskConcierge is true, so the bug does not reproduce. Reproducing the reported failure requires a fresh account with no Concierge report yet.

Step	Status	Observation
Home shows the "Ask Concierge…" composer with + and Send	pass	+ icon, text field, and Send present in the row
Clicking + opens the attachment menu	pass	"Add attachment" popover opened
Typing text enables Send	pass	Send changed from disabled grey to enabled green

Data flow: sign out → sign back in → App.openApp() / reconnectApp() fires; CONCIERGE_REPORT_ID and its REPORT record are unset until the response lands (or never, on accounts with no Concierge chat) → shouldShowAskConcierge = false → + and Send disabled → user taps +, nothing happens; the lazy report-creation path is never reached.

This is App-only code (all references are in Expensify/App), so no cross-repo escalation is needed.

Evidence (3)

Home tab with Ask Concierge composer visible

Add attachment popover opened by the + button

Composer with typed text and Send button enabled

---

Next Steps for Contributor+ team:
To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/99568) to create a draft PR.
To refine: @MelvinBot <your feedback>
To reject: Explain why you are rejecting Melvin's proposal.

---

view run

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @Ollyws (External)

[melvin-bot]

Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue.

[yusufdeveloper2903]

Melvin's root cause is right, but the "+" flow has a second !reportID guard that the proposal doesn't touch — the attachment picker bails before askConciergeWithAttachment ever runs, so removing the early return in useAskConcierge never makes navigateToConciergeChat's creation path reachable from "+":

App/src/pages/home/ForYouSection/useConciergeAttachmentPicker.ts

Lines 24 to 27 in c80d595

	const onFilesValidated = (files: FileObject[]) => {
	if (files.length === 0 || !reportID) {
	return;
	}

So with conciergeReportID still empty, simply enabling the button turns "+ does nothing" into "+ opens a menu whose only item does nothing" — Add attachment → pick a file → silent return at that guard, no report created.

Happy to put up a full proposal for this if that's useful

[puneetlath]

Closing in favor of https://github.com/Expensify/Expensify/issues/675533. We'll handle on the BE there.