mWeb - Per diem-Unable to submit a Per diem expense

[IuliiaHerets]

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.0.81-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 TestRail: #54252
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: Samsung S23FE/ Android 14
App Component: Money Requests

Action Performed:

Precondition
Workspace has Per diem enabled and Per diem rates loaded.

Steps:

1. Go to staging.new.expensify.com
2. Tap on FAB > Create expense > Per diem tab
3. Select any country
4. Select start and end dates
5. Select any Subrate
6. Enter a valid Quantity
7. Tap Save
8. Tap Submit expense

Expected Result:

The Per diem expense is submitted.

Actual Result:

After tapping the Submit expense button, the Per diem expense is not submitted. The Confirm details page remains with the details switching to grey color.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6707585_1736199355398.Unable_submit_Per_diem.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @sonialiap (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.

[melvin-bot]

Triggered auto assignment to @blimpich (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.