[Due for payment 2026-09-04] Home - Draft text is not cleared after clearing cache in Home search box.

[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: V9.4.61-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: #98336
Email or phone of affected tester (no customers): dreamnitethedragon+vegst@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Redmi note 10s android 13
App Component: User Settings

Action Performed:

1. Launch app
2. In Home, search box enter a text
3. Go to troubleshoot - clear cache
4. Go to Home and note text is not cleared
5. Go to concierge
6. Enter a text
7. Go to troubleshoot and clear cache
8. Go to to Concierge
9. Note draft text is cleared

Expected Result:

Draft text must be cleared after clearing cache in Home search box.

Actual Result:

Draft text is not cleared after clearing cache in Home search box.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7243175_1787740981157.Screenrecorder-2026-08-26-16-08-06-15.mp4

View all open jobs on GitHub

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

Issue Owner

Current Issue Owner: @ZhenjaHorbach

[applause-bot]

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

[melvin-bot]

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

[melvin-bot]

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

[github-actions]

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

[melvin-bot]

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

[melvin-bot]

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

[MelvinBot]

🔍 Investigation Summary

Classification: Frontend bug
Causing PR: #98336 - "[Home Page] Add Concierge prompt box to home For You section" by @adamgrzybowski (High confidence)
Related Issues: #94497 (feature request implemented by the PR)

Recommendation: ROLL FORWARD

The confirmed cause is a brand-new feature; reverting the whole ~266-line PR (plus attachment/date/style refactors) is disproportionate for a stale-draft edge case that only appears after a manual "Clear cache". A small targeted fix is preferable. Note: severity is low (no data loss, no crash, functionality unaffected), so the team may reasonably choose to DEMOTE — but I am keeping DeployBlockerCash because an App PR caused the bug and I do not remove App-deploy blocker labels for App-caused issues.

Assigned: @adamgrzybowski (PR author), @puneetlath and @ZhenjaHorbach (approving reviewers) — already assigned on the issue.
Labels: No changes. Only DeployBlockerCash was present; this is a Frontend bug so it is correctly kept. No DeployBlocker (Web) label was present to remove.

📋 Detailed Analysis

Evidence

• The "Home search box" in the repro is the new Concierge prompt box on the Home "For You" section, added exclusively by PR [Home Page] Add Concierge prompt box to home For You section #98336 (src/pages/home/ForYouSection/ConciergePromptBox.tsx is a new file in that PR). This is a new feature not present in production, which matches "reproducible in staging, N/A in prod".
• The PR is the only change in the current staging deploy (Deploy Checklist Deploy Checklist: New Expensify 2026-08-25 #99466) that introduces a text input on the Home page.

Verification

• Affected file: src/pages/home/ForYouSection/ConciergePromptBox.tsx (new in PR [Home Page] Add Concierge prompt box to home For You section #98336).
• The prompt box stores its draft in component-local React state, not Onyx:
  • const [value, setValue] = useState(''); — ConciergePromptBox.tsx#L69
  • clearInput only resets that local state — ConciergePromptBox.tsx#L79-L82
• The working comparison (report/Concierge comment draft) is Onyx-backed, which is why it clears:
  • const [draftComment] = useOnyx(\${ONYXKEYS.COLLECTION.REPORT_DRAFT_COMMENT}${reportID}`);` — ComposerProvider.tsx#L50
• "Clear cache" (Troubleshoot) calls clearOnyxAndResetApp, which wipes Onyx storage (clearOnyxAndSeedFullReconnect(KEYS_TO_PRESERVE)) but does not unmount/remount the React tree — App.ts#L924-L978.

Root Cause

"Clear cache" clears Onyx, not React component state. The Concierge comment composer reads its draft from Onyx (REPORT_DRAFT_COMMENT), so wiping Onyx makes it re-render empty — correct behavior. The new Home Concierge prompt box holds its draft only in useState('') (ConciergePromptBox.tsx#L69), which survives the Onyx wipe because the component is never remounted. Result: the Home box keeps its stale text while report comment drafts clear.

Suggested fix

Targeted, roll-forward fix (no revert needed). Either:

1. Persist the prompt-box draft to a dedicated Onyx key read via useOnyx (mirroring the REPORT_DRAFT_COMMENT pattern), so clearOnyxAndResetApp clears it automatically; or
2. If keeping the draft local is intentional, reset the local state when the app resets — e.g. subscribe to the same reset signal / clear on Onyx-cleared so clearInput() runs during cache clear.

Option 1 is the more consistent approach and matches how every other composer draft behaves across the app.