Home - No "The maximum comment length is 15,000 characters" error on Concierge prompt 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: 9.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): sdjonisdjoisdjio@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:

1. Go to staging.new.expensify.com
2. Paste text more than 15000 characters on Concierge prompt box.
3. Click Send.

Expected Result:

"The maximum comment length is 15,000 characters" error will appear on input field.

Actual Result:

"The maximum comment length is 15,000 characters" error does not appear on input field when sentence has more than 15000 characters.
Error shows up after sending the sentence.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7242772_1787693902791.2.mp4

View all open jobs on GitHub

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

[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/08d8890ac44ddfc9d34ddf90a3242efec1c1d72e0e300e29ee88cf968a32397a

[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 (the feature request implemented by the PR)

Recommendation: ROLL FORWARD (targeted fix)

PR #98336 is a large, brand-new feature (266-line new component plus tests) that is not in production. A targeted fix that wires up the existing comment-length validation into the new composer is far simpler and safer than reverting the whole feature.

Assigned: @adamgrzybowski (PR author), @ZhenjaHorbach and @puneetlath (approving reviewers) from the causing PR
Labels: No label change. DeployBlockerCash is kept because this is a frontend bug with a causing App PR. DeployBlocker was not present, so nothing was removed.

📋 Detailed Analysis

Evidence

• PR [Home Page] Add Concierge prompt box to home For You section #98336 introduced src/pages/home/ForYouSection/ConciergePromptBox.tsx as a new file (266 additions, 0 deletions), which is the Concierge prompt box on the Home "For You" section — exactly the input described in the repro steps.
• Reproducible on staging, N/A in production because the whole feature is new — consistent with the bug being introduced by this PR.
• The new prompt box builds its own composer from the raw Composer component and its own submit path, and it never runs the max-comment-length validation that the standard report composer uses. So when the user pastes > 15,000 characters, no inline error is shown; the error only appears later, after the message is sent into the resulting Concierge chat (which uses the normal report composer).

Verification

• Affected file (new, from this PR): src/pages/home/ForYouSection/ConciergePromptBox.tsx
  • Composer is rendered with only value/onChangeText/selection wiring and no length check: lines 218-234.
  • canSubmit and submit only gate on shouldShowAskConcierge and a non-empty trimmed value — no max-length gate: lines 114-122.
  • No ExceededCommentLength / useDebouncedCommentMaxLengthValidation import or usage anywhere in the component.
• Reference implementation the standard composer uses (not touched by this PR, so the timeline confirms the new composer simply never adopted it):
  • Validation hook: useDebouncedCommentMaxLengthValidation.ts computes getCommentLength(value) > CONST.MAX_COMMENT_LENGTH.
  • Error UI: ComposerExceededLength.tsx rendering ExceededCommentLength.tsx with the composer.commentExceededMaxLength copy ("The maximum comment length is 15,000 characters").

Root Cause

The new ConciergePromptBox is a bespoke composer that does not reuse the comment-length validation the standard ReportActionCompose runs. Because nothing computes getCommentLength(value) > CONST.MAX_COMMENT_LENGTH as the user types/pastes, the app never (a) renders the ExceededCommentLength inline error, (b) applies the red error border, or (c) disables the send button. The 15,000-character limit is only enforced downstream once the message lands in the real Concierge report composer, which is why the error appears only after sending.

Suggested targeted fix

In ConciergePromptBox.tsx:

1. Call useDebouncedCommentMaxLengthValidation({reportID: conciergeTargetReportID}) and invoke debouncedCommentMaxLengthValidation(value) from onChangeText (alongside setValue).
2. Include !isExceedingMaxLength in canSubmit (line 114) so send is blocked while over the limit.
3. Render <ExceededCommentLength maxCommentLength={exceededMaxLength} /> below the composer when exceededMaxLength is set, and apply the danger/red-border style to the compose box wrapper (line 143) when exceeded, mirroring the standard composer.