Expense - IOU sender can pay the expense and error shows up

[applause-bot]

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

Action Performed:

1. Go to staging.new.expensify.com
2. Open 1:1 DM with any user.
3. Submit an expense to the user.
4. Click Mark as paid.

Expected Result:

IOU sender should not be able to pay the expense.

Actual Result:

IOU sender can pay the expense and error shows up.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

To be added by Applause Leads

View all open jobs on GitHub

Bug7202172_1783450037412.3.mp4

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7202172

Issue Owner

Current Issue Owner: @dmkt9

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/60ecf1fa3b9ac2de87b135a3020d9642821e6feb4d1f2516cfd1471117ee10b1

[melvin-bot]

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

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

[mjasikowski]

@NikkiWines this comes from #92787