[RCA #72674] Expense - Different label on green button when submitting 0.00 expense in workspace & self DM

[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.2.60-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: #72674
Email or phone of affected tester (no customers): sjdsjnodijsisjio@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Account has self DM.

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Click + > Create expense > Manual.
4. Enter 0 > Next.
   → Green button on confirm page shows Create RM0.00 expense.
5. Close the RHP.
6. Go to self DM.
7. Click + > Create expense > Manual.
8. Enter 0 > Next.
   → Green button on confirm page shows Create expense.

Expected Result:

In Step 4 and 8, when submitting 0.00 expense in workspace chat and self DM, the green button on confirm page should have the same label.

Actual Result:

In Step 4, when submitting 0.00 expense in workspace chat, the green button on confirm page shows Create RM0.00 expense.
In Step 8, when submitting 0.00 expense in self DM, the green button on confirm page shows Create expense.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7007300_1763469763117.3.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @arosiclair (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

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

[arosiclair]

This is minor I'm going to demote.