[Due for payment 2026-03-18] [$250] Expense-Amount is out of view when max number of digits is applied, Save button shifts to left

[mitarachim]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.3.11-23
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: #80163
Email or phone of affected tester (no customers): sidnjosdnjdosijsojns@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Click + > Create expense > Manual.
4. Enter MYR 8888888888.88 (use MYR currency).
5. Click Next.
6. On confirm page, click Amount.

Expected Result:

• Amount will not be out of view.
• Save button will not shift to left.

Actual Result:

• Amount is out of view when max number of digits is applied.
• Save button shifts to left.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7064903_1770091425039.07.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022018783932587207542
• Upwork Job ID: 2018783932587207542
• Last Price Increase: 2026-02-03

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @johncschuster (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

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

[OSBotify]

🔍 Investigation Summary

Classification: Frontend bug
Causing PR: #80163 - "feat: increase max allowed number of digits for manual expenses" by @samranahm (High confidence)
Related Issues: #78643 (original feature request)

Recommendation: REVERT

This PR introduced a UI layout issue by increasing the maximum amount length from 8 to 10 digits without accounting for the layout constraints on the confirmation page. When maximum-length amounts are entered (e.g., MYR 8888888888.88), the amount overflows its container and causes the Save button to shift left.

Labels: Keeping DeployBlockerCash (blocks App deploy). Removing DeployBlocker (does not block backend deploy).

📋 Detailed Analysis

Evidence

• The bug appears on staging (version 9.3.11-23) and is not in production, confirming it was introduced by a recent PR
• Melvin-bot correctly identified PR feat: increase max allowed number of digits for manual expenses #80163 as the causing PR
• The issue description states this is a "new feature, doesn't exist in prod"
• The bug manifests when entering the maximum allowed digits (10) for amounts with certain currencies like MYR

Verification

Files affected by the bug:

• src/components/MoneyRequestAmountInput.tsx - Displays the amount on the confirmation page
• src/components/NumberWithSymbolForm.tsx - Underlying form component
• src/components/MoneyRequestConfirmationList.tsx - The confirmation page layout

PR #80163 modifications:

• Changed CONST.IOU.AMOUNT_MAX_LENGTH from 8 to 10 digits
• Updated AmountWithoutCurrencyInput.tsx mask pattern to allow 10 digits
• Updated validation regex to accept 10 digits instead of 8
• Modified multiple validation points throughout the codebase

Root Cause

The PR increased the maximum allowable amount length from 8 to 10 digits to support larger expense amounts. However, the UI components that display these amounts (particularly MoneyRequestAmountInput and its underlying NumberWithSymbolForm) do not properly handle the increased length. When amounts reach the new maximum (e.g., "8888888888.88"), the text overflows its container because:

1. The input mask now allows [0999999999] instead of [09999999] (2 extra digits)
2. The display components likely have fixed or max-width constraints designed for 8-digit amounts
3. No responsive layout adjustments were made to accommodate the longer text
4. This causes the amount to render outside the visible area and pushes adjacent elements (like the Save button) out of their intended positions

The fix should either:

• Revert this PR and re-implement with proper UI layout adjustments
• Roll forward with layout fixes to properly contain/wrap/truncate long amounts