[Due for payment 2026-09-02] Android & iOS - Home - For You prompt requires two taps to send a message

[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.4.61-0
Reproducible in staging?: Yes
Reproducible in production?: No
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): jose.sat94+10jul@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Samsung Galaxy S21/Android 15, iPhone 13/18.6.2
App Component: Other

Action Performed:

1. Launch Expensify app
2. Log in with valid credentials
3. Open the Home page
4. Locate the "For You" section
5. Tap the prompt box
6. Type a message
7. Tap the send button

Expected Result:

The compose box is focused with a single tap, and the message is sent with a single tap on the send button.

Actual Result:

The user needs to tap the send button twice for the message to be sent.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7242800_1787696292326.A.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7242800

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/699f77781218df5346626e09e802d04d290f4922a070aed64e88956d67be8e80

[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 "For You" Concierge prompt box is a brand-new feature (not in production), and the two-tap bug is a small, well-understood native focus/keyboard interaction that the app already solves elsewhere. A targeted fix is safer than reverting a 38-file feature PR that also touches shared attachment-modal code. Revert is a viable fallback if a fix can't land quickly.

Assigned: @adamgrzybowski (PR author), @puneetlath and @ZhenjaHorbach (approving reviewers) from PR #98336
Labels: No changes. DeployBlockerCash is correct and retained (App-side fix required); no DeployBlocker was present.

📋 Detailed Analysis

Evidence

• The bug is scoped to the "For You" Concierge prompt box, a UI element that did not exist before PR [Home Page] Add Concierge prompt box to home For You section #98336. The PR adds it as a brand-new file (src/pages/home/ForYouSection/ConciergePromptBox.tsx, +266/-0).
• PR [Home Page] Add Concierge prompt box to home For You section #98336 merged 2026-08-25 and is item Show a list of reports in the sidebar #24 in the current StagingDeployCash (Deploy Checklist: New Expensify 2026-08-25 #99466). The issue reproduces on staging but not production, consistent with a regression from a PR in this staging deploy.
• The symptom ("must tap send twice") is a classic React Native keyboard-dismissal race, described below.

Verification

• Affected file: src/pages/home/ForYouSection/ConciergePromptBox.tsx lines 250-258 — the send button is a plain SubmitDraftButton with onPress={submit} (a PressableWithFeedback).
• The box is rendered inside the HomePage ScrollView at src/pages/home/HomePage.tsx lines 64-67, which does not set keyboardShouldPersistTaps, so it uses React Native's default of "never".
• Contrast the working chat composer ComposerSendButton.tsx lines 39-70, which wraps the same SubmitDraftButton in a GestureDetector/Gesture.Tap() and adds onMouseDown={(e) => e.preventDefault()} specifically to "Keep focus on the composer when Send message is clicked." The new prompt box omits both.

Root Cause

With keyboardShouldPersistTaps="never" (the ScrollView default), when the compose input is focused and the soft keyboard is up, the first tap outside the TextInput is consumed by React Native to dismiss the keyboard and blur the input — it never reaches the send button's onPress. The second tap (keyboard now dismissed) actually fires submit(). Hence "two taps to send."

The chat composer avoids this by handling the press through react-native-gesture-handler (Gesture.Tap() in a GestureDetector), which recognizes the tap at the native gesture level regardless of the ScrollView's keyboardShouldPersistTaps, plus onMouseDown preventDefault() to preserve focus on web. ConciergePromptBox uses a plain onPress, so it is subject to the keyboard-dismissal race.

Suggested fix direction: mirror ComposerSendButton — wrap the SubmitDraftButton in a GestureDetector with a Gesture.Tap() that calls submit() (and add onMouseDown preventDefault on the wrapper for web), rather than relying on onPress. Alternatively, set keyboardShouldPersistTaps="handled" on the surrounding ScrollView, though the gesture-based approach is the established pattern here and is more localized.

---

view run