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
[Due for payment 2026-10-08] [$175] Android - Report - Report title box is not automatically expanded with new line of text. #99718
Version Number: 9.4.63-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:#97489 Email or phone of affected tester (no customers):ibellicotest+2766@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Motorola MotoG60 / Android 12 (Hybrid app) App Component: Money Requests
Action Performed:
Prerequisite: Account has a workspace.
Open the Expensify app.
Navigate to workspace chat.
Create a manual expense.
Open the just created expense and tap on the title to edit it.
Start typing on title box, until more lines of text are created.
Note that when a third line of text is reached, box is not expanded until text reaches the middle of the line.
Expected Result:
Report title box should be automatically expanded when text reaches new lines.
Actual Result:
Report title box is not expanded when a third line of text is reached. Box is only expanded after text reaches near the end of the new line.
👋 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.
Classification: Frontend bug Causing PR: #97489 - "Let single-field edit input grow to reduce wasted white space" by @MelvinBot (High confidence) Related Issues: #96905 (the issue #97489 was fixing)
Recommendation: REVERT
PR #97489 is a self-contained, presentational feature PR that introduced the entire auto-grow behavior on the report title editor; the regression exists only on staging (the feature doesn't exist in production), so a clean revert fully restores known-good behavior and unblocks the App deploy. A targeted roll-forward is possible but riskier under deploy-blocker time pressure (see Root Cause).
Assigned: @MelvinBot (PR author, already assigned by melvin-bot), @chuckdries and @mkhutornyi (approving reviewers, already assigned) Labels: No change. DeployBlockerCash correctly stays (App PR is the cause). No DeployBlocker present to remove.
The bug is reproducible on staging only; production is N/A because the auto-grow behavior on the title box did not exist before this PR. Before Let single-field edit input grow to reduce wasted white space #97489 the title input was a fixed single-line box, so there was no "expand on new line" behavior to regress — this PR created it.
PR Let single-field edit input grow to reduce wasted white space #97489 explicitly enables the grow behavior for exactly this input: EditReportFieldText.tsx (the report title / text report field editor) gains the autoGrowSingleLine prop, which maps to autoGrowHeight + maxAutoGrowHeight = variables.textInputAutoGrowMaxHeight (115px).
Verification
Affected feature: the report-title edit box auto-expanding as text wraps. Rendered by src/pages/EditReportFieldText.tsx, backed by src/components/TextInput/BaseTextInput/index.tsx and the auto-grow measurement in src/components/TextInput/TextInputMeasurement/index.tsx + src/components/TextInput/BaseTextInput/implementation/index.native.tsx.
The auto-grow height is not measured from the visible TextInput — it is measured from a separate hidden Text in TextInputMeasurement, whose reported layout height drives the container height:
TextInputMeasurement/index.tsx — the hidden TextonLayout calls onSetTextInputHeight(e.nativeEvent.layout.height):
{/* \u200B added to solve the issue of not expanding the text input enough when the value ends with '\n' (https://github.com/Expensify/App/issues/21271) */}
The box grows only when the hidden measurement Text wraps to a new line. That element's wrap point is not perfectly aligned with the visible input's wrap point on native Android:
The measurement path applies a +2px width compensation only for Safari / mobile Safari / mobile Chrome, and none for Android native:
When the measurement element is even slightly wider than the visible input, the visible input wraps onto the third line first while the hidden measurement Text still measures two lines. The container height therefore does not grow until enough additional characters are typed to also wrap the (slightly wider) hidden measurement element — i.e. "the box is not expanded until the text reaches the middle of the line," exactly as reported. This is a pre-existing quirk of the autoGrowHeight measurement path that #97489 newly exposed by turning it on for the single-line title box (where the lag is very visible), rather than a bug in brand-new logic.
Because the fix lives in shared, platform-sensitive measurement code, a precise roll-forward (reconciling Android measurement width / line-height with the visible input) needs on-device verification and carries regression risk for the other consumers of autoGrowHeight (e.g. RoomDescriptionPage, IOURequestStepDescription). Reverting #97489 is the lower-risk path to unblock the deploy; the feature can be re-landed with the Android measurement-width fix.
@jawad-erfani thanks for the feedback. We don't currently have a process for paying out issues without the Help Wanted label, unfortunately. Reasoning, we don't want to open up all issues to contributor comments (ie. Contributor AI bots) because it takes more review time from those involved. If/when we do, we add the Help Wanted label (and, these days, a dozen or more proposals get posted near-immediately, for better/worse).
@chuckdries and I have been discussing this for weeks and there might be an update at some point.
Activity
melvin-bot commentedon Aug 28, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #97489
applause-bot commentedon Aug 28, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/72c329859b25dc5e81bc1f09e5f4b11a468e18a2cb2788fa8505faa1b5bcf8df
melvin-bot commentedon Aug 28, 2026
@chuckdries @mkhutornyi you have been assigned to this deploy blocker because you reviewed the offending PR: #97489
melvin-bot commentedon Aug 28, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Aug 28, 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:
MelvinBot commentedon Aug 28, 2026
🔍 Investigation Summary
Classification: Frontend bug
Causing PR: #97489 - "Let single-field edit input grow to reduce wasted white space" by @MelvinBot (High confidence)
Related Issues: #96905 (the issue #97489 was fixing)
Recommendation: REVERT
PR #97489 is a self-contained, presentational feature PR that introduced the entire auto-grow behavior on the report title editor; the regression exists only on staging (the feature doesn't exist in production), so a clean revert fully restores known-good behavior and unblocks the App deploy. A targeted roll-forward is possible but riskier under deploy-blocker time pressure (see Root Cause).
Assigned: @MelvinBot (PR author, already assigned by melvin-bot), @chuckdries and @mkhutornyi (approving reviewers, already assigned)
Labels: No change.
DeployBlockerCashcorrectly stays (App PR is the cause). NoDeployBlockerpresent to remove.📋 Detailed Analysis
Evidence
v9.4.63-0where the bug reproduces.EditReportFieldText.tsx(the report title / text report field editor) gains theautoGrowSingleLineprop, which maps toautoGrowHeight+maxAutoGrowHeight = variables.textInputAutoGrowMaxHeight(115px).Verification
src/pages/EditReportFieldText.tsx, backed bysrc/components/TextInput/BaseTextInput/index.tsxand the auto-grow measurement insrc/components/TextInput/TextInputMeasurement/index.tsx+src/components/TextInput/BaseTextInput/implementation/index.native.tsx.a1a3c8c):EditReportFieldText.tsxaddsautoGrowSingleLineto the title input: https://github.com/Expensify/App/blob/a1a3c8cc33f21bc9398ba47c39927f3593e2b384/src/pages/EditReportFieldText.tsxBaseTextInput/index.tsxwiresautoGrowSingleLine→autoGrowHeightand defaultsmaxAutoGrowHeightto 115px: https://github.com/Expensify/App/blob/a1a3c8cc33f21bc9398ba47c39927f3593e2b384/src/components/TextInput/BaseTextInput/index.tsx#L65-L96Root Cause
The auto-grow height is not measured from the visible
TextInput— it is measured from a separate hiddenTextinTextInputMeasurement, whose reported layout height drives the container height:TextInputMeasurement/index.tsx— the hiddenTextonLayoutcallsonSetTextInputHeight(e.nativeEvent.layout.height):App/src/components/TextInput/TextInputMeasurement/index.tsx
Lines 89 to 103 in a6bc76a
autoGrowHeightInputContainer(textInputHeight, minHeight, maxHeight)=clamp(textInputHeight, minHeight, maxHeight):App/src/styles/index.ts
Lines 6663 to 6667 in a6bc76a
The box grows only when the hidden measurement
Textwraps to a new line. That element's wrap point is not perfectly aligned with the visible input's wrap point on native Android:+2pxwidth compensation only for Safari / mobile Safari / mobile Chrome, and none for Android native:App/src/components/TextInput/TextInputMeasurement/index.tsx
Lines 93 to 98 in a6bc76a
When the measurement element is even slightly wider than the visible input, the visible input wraps onto the third line first while the hidden measurement
Textstill measures two lines. The container height therefore does not grow until enough additional characters are typed to also wrap the (slightly wider) hidden measurement element — i.e. "the box is not expanded until the text reaches the middle of the line," exactly as reported. This is a pre-existing quirk of theautoGrowHeightmeasurement path that #97489 newly exposed by turning it on for the single-line title box (where the lag is very visible), rather than a bug in brand-new logic.Because the fix lives in shared, platform-sensitive measurement code, a precise roll-forward (reconciling Android measurement width / line-height with the visible input) needs on-device verification and carries regression risk for the other consumers of
autoGrowHeight(e.g.RoomDescriptionPage,IOURequestStepDescription). Reverting #97489 is the lower-risk path to unblock the deploy; the feature can be re-landed with the Android measurement-width fix.view run
mkhutornyi commentedon Aug 28, 2026
Not blocker. The bug exists in production (playstore app)
prod.mov
51 remaining items
melvin-bot commentedon Oct 7, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Oct 7, 2026
Payment Summary
Resolving PRs:
Match the autoGrowHeight measurement text's line breaking to the input on Android #102149
Reviewer: @mkhutornyi owed $175 via NewDot
BugZero Checklist (@mallenexpensify)
melvin-bot commentedon Oct 12, 2026
@mallenexpensify Eep! 4 days overdue now. Issues have feelings too...
mallenexpensify commentedon Oct 14, 2026
Payment Summary
Contributor+: @mkhutornyi due $250 via NewDot
mallenexpensify commentedon Oct 14, 2026
@jawad-erfani thanks for the feedback. We don't currently have a process for paying out issues without the
Help Wantedlabel, unfortunately. Reasoning, we don't want to open up all issues to contributor comments (ie. Contributor AI bots) because it takes more review time from those involved. If/when we do, we add theHelp Wantedlabel (and, these days, a dozen or more proposals get posted near-immediately, for better/worse).@chuckdries and I have been discussing this for weeks and there might be an update at some point.
trjExpensify commentedon Oct 15, 2026
approved $250 for @mkhutornyi