[Due for payment 2026-03-30] Split - Negative sign can be added on Amount field, but not Percent field

[nlemma]

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.39-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: #81905
Email or phone of affected tester (no customers): sdjsdjosijnsodiosd@gmail.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:

• Use Samsung keyboard only.

1. Launch Expensify app.
2. Go to workspace chat.
3. Create an expense.
4. Open the expense report.
5. Tap More > Split.
6. Tap on any amount field.
7. Enter negative amount.
8. Switch to Percent.
   → Negative sign is populated in amount field.
9. Tap on any percentage field.
10. Try to add negative percentage.

Expected Result:

User should be able to add negative sign in percentage field because negative sign can be added from Amount tab and the sign is carried to Percent tab.

Actual Result:

User can add negative sign in Amount field, but not Percent field.
On web, negative sign can be added on Percent field.

This issue is only reproducible on Samsung keyboard and not Google keyboard.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7105365_1773757631502.Screen_Recording_20260317_222306_Expensify.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

[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: #81905 - "Add support to splits for negative values" by @kubabutkiewicz (High confidence)
Related Issues: None

Recommendation: REVERT

The PR correctly implemented the logic to support negative percentages but introduced an inconsistency in keyboard configuration between Amount and Percent fields, making it impossible to enter negative values in the Percent field on Samsung keyboard.

Labels: No label changes - keeping DeployBlockerCash as this is a frontend bug in App that blocks the App deploy.

📋 Detailed Analysis

Evidence

PR #81905 was explicitly designed to add support for negative values in splits. The PR:

• Added allowNegative prop to PercentageForm and passed it to SplitPercentageInput
• Modified the validation logic to support negative percentages
• Updated SplitAmountInput to use NUMBERS_AND_PUNCTUATION keyboard type (which includes minus sign)
• But did NOT update PercentageForm to use a keyboard type that supports minus sign

The melvin-bot automatically assigned this issue to the PR author, and the issue is reproducible only in staging (version 9.3.39-0), where this PR was just merged.

Verification

I verified the PR modifies the exact files involved in split functionality:

Amount Field (working correctly):

• File: src/components/SelectionList/ListItem/SplitListItem/SplitAmountInput.tsx
• Line 58: keyboardType={CONST.KEYBOARD_TYPE.NUMBERS_AND_PUNCTUATION}
• This keyboard includes the minus sign, allowing negative input

Percent Field (broken):

• File: src/components/PercentageForm.tsx
• Line 81: keyboardType={CONST.KEYBOARD_TYPE.DECIMAL_PAD}
• This keyboard does NOT include the minus sign on Samsung keyboard
• The component accepts allowNegative={true} prop but uses a keyboard without minus key

Root Cause

The PR added comprehensive logic to support negative percentages (validation, calculation, display), but overlooked the keyboard configuration for percentage input.

On Samsung keyboard specifically, DECIMAL_PAD does not expose a minus sign key, while NUMBERS_AND_PUNCTUATION does. This keyboard behavior difference between manufacturers is why:

• Web works (keyboard always has minus key)
• Google keyboard works (shows minus on decimal pad)
• Samsung keyboard fails (no minus on decimal pad)

The fix requires updating PercentageForm.tsx to accept and use a keyboardType prop (similar to how the PR updated other components), and passing KEYBOARD_TYPE.NUMBERS_AND_PUNCTUATION from SplitPercentageInput.