BNP - There's double negative in creating negative amount expense

[jponikarchuk]

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: v9.2.86-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #76548
Email or phone of affected tester (no customers): applausetester+piyoh@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Windows 11 / Chrome
App Component: Money Requests

Action Performed:

Preconditions: Logged in to any account
Steps:

1. Click FAB
2. Click "Create expense"
3. Click "Flip" to make amount as negative in BNP
4. Enter any number
5. Click "Next" -> notice it's not running smoothly and there are double negative sign before the currency and before the amount
6. Click back icon (<) on RHN to back to the BNP again

Expected Result:

1. After clicking "Next" in BNP, creating expense process should run smoothly
2. After clicking back (<) icon on RHN to back to the BNP again, the negative sign should only display 1 before the currency

Actual Result:

1. After clicking "Next" in BNP, it's not running smoothly and there are double negative sign before the currency and before the amount
2. After clicking back (<) icon on RHN to back to the BNP again, there are double negative sign before the currency and before the amount, also after clicking back, user can't continue to the next page again

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

[melvin-bot]

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

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