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
[hold for #82586] Android & iOS - Expense - Unable to add space or a new line in Description field #87400
Version Number: 9.3.54-2 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack:#86923 Email or phone of affected tester (no customers):applausetester+sjois2jd@applause.expensifail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Samsung Galaxy S25 FE / Android 16 App Component: Money Requests
Action Performed:
Precondition:
Log in with Expensifail account.
Launch Expensify app.
Open FAB > Create expense > Manual.
Enter amount > Next.
Tap Description field.
Scroll down if needed.
Type anything, then add space or a new line.
Expected Result:
User can add space or a new line in Description field.
Actual Result:
User cannot add space or a new line in Description field.
👋 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.
Investigation Summary: Frontend bug. Causing PR: #86923 (Manual expense flow UI refactor r2 by @ChavdaSachin, High confidence). Recommendation: REVERT. PR 86923 introduced an inline TextInput for the Description field (when the newManualExpenseFlow flag is enabled). The setMoneyRequestDescription function at line 1279 of src/libs/actions/IOU/index.ts calls comment.trim() on every keystroke before persisting to Onyx. Since the TextInput is a controlled component whose value comes from Onyx, any trailing space or newline is immediately stripped before re-render, making it impossible to type spaces or newlines. The non-split path trims on every change event, unlike the split path which correctly defers trimming to submission. Reverting is the safest path since this is a staging-only regression. Assigned: @ChavdaSachin (author), @joekaufmanexpensify, @ShridharGoel, @puneetlath (approving reviewers). Labels: DeployBlockerCash is correct and no label changes are needed.
Activity
melvin-bot commentedon Apr 8, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #86923
melvin-bot commentedon Apr 8, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Apr 8, 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:
OSBotify commentedon Apr 8, 2026
Investigation Summary: Frontend bug. Causing PR: #86923 (Manual expense flow UI refactor r2 by @ChavdaSachin, High confidence). Recommendation: REVERT. PR 86923 introduced an inline TextInput for the Description field (when the newManualExpenseFlow flag is enabled). The setMoneyRequestDescription function at line 1279 of src/libs/actions/IOU/index.ts calls comment.trim() on every keystroke before persisting to Onyx. Since the TextInput is a controlled component whose value comes from Onyx, any trailing space or newline is immediately stripped before re-render, making it impossible to type spaces or newlines. The non-split path trims on every change event, unlike the split path which correctly defers trimming to submission. Reverting is the safest path since this is a staging-only regression. Assigned: @ChavdaSachin (author), @joekaufmanexpensify, @ShridharGoel, @puneetlath (approving reviewers). Labels: DeployBlockerCash is correct and no label changes are needed.
19 remaining items
joekaufmanexpensify commentedon Jun 1, 2026
Held
joekaufmanexpensify commentedon Jun 8, 2026
Still held
joekaufmanexpensify commentedon Jun 15, 2026
Same!
joekaufmanexpensify commentedon Jun 22, 2026
@ChavdaSachin can we take this off hold yet?
joekaufmanexpensify commentedon Jun 24, 2026
Pending input
joekaufmanexpensify commentedon Jul 6, 2026
@ChavdaSachin mind confirming this?
joekaufmanexpensify commentedon Jul 13, 2026
Bump @ChavdaSachin
joekaufmanexpensify commentedon Jul 20, 2026
Bumped in Slack.
ChavdaSachin commentedon Jul 21, 2026
Thanks for the Slack ping @joekaufmanexpensify.
This issue is resolved and could be closed.
Screen.Recording.2026-07-21.at.9.09.37.PM.mov
joekaufmanexpensify commentedon Jul 27, 2026
Thank you! Closing as this is all set.