[Due for payment 2025-06-17] [$250] Invoice - Invoice from a deleted workspace can be paid from invoice details

[vincdargento]

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.1.45-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/cases/view/3073290
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: Windows 10 / Chrome, Samsung Galaxy A12 / Android 13
App Component: Money Requests

Action Performed:

Precondition: User A has sent an invoice to user B

1. Go to staging.new.expensify.com
2. Access the invoice room as both user
3. As user A, delete the workspace associated with the invoice
4. As user B, click on the invoice preview

Expected Result:

Pay button not displayed in preview and details view

Actual Result:

Pay button is displayed in invoice details view

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

bug.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021924522474185440610
• Upwork Job ID: 1924522474185440610
• Last Price Increase: 2025-05-19
• Automatic offers:
• linhvovan29546 | Contributor | 107382530

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @maddylewis

[melvin-bot]

Triggered auto assignment to @maddylewis (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 @aldo-expensify (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

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

[melvin-bot]

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

[vincdargento]

@maddylewis FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

[aldo-expensify]

I'm investigating this, I reproduced in dev but still haven't found the cause

[aldo-expensify]

This also happens in production:

No idea if this behaviour changed on purpose.