Spend - Unable to submit expense by bulk select

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

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

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create an expense.
4. Go to Spend > Expenses.
5. Select the expense via checkbox.
6. Click dropdown button > Submit.
7. Select the expense via checkbox.
8. Click dropdown button.

Expected Result:

Expense will be submitted.
Submit button will no longer appear.

Actual Result:

Expense is not submitted.
Submit button remains.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7232099_1786568060680.7.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7232099

[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/bf72347d88bf3d2ca1feda917ad4a7bec68850d2aeb70182e687c7db6aecb037

[melvin-bot]

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

[melvin-bot]

@mountiny @QichenZhu you have been assigned to this deploy blocker because you reviewed the offending PR: #98305

[melvin-bot]

@BartekObudzinski you have been assigned to this deploy blocker because you authored the offending PR: #98305

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