[HOLD for payment 2024-12-03] [Search v1.2] Android - Expense - Unexpected error when submitting expense to same WS after paying another

[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.60-0
Reproducible in staging?: Y
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5204723&group_by=cases:section_id&group_order=asc&group_id=319502
Issue reported by: Applause Internal Team

Action Performed:

1. Open the Expensify app.
2. Tap on the FAB and select "Submit Expense"
3. Complete the expense creation process and send the expense to any workspace.
4. Tap on "Search" on the bottom of the screen.
5. Tap on "Outstanding"
6. Tap on "Pay" on the preview of the just created expense.
7. Tap on the FAB and select "Submit Expense"
8. Complete the expense creation flow and send the expense to the same workspace of the just paid expense.
9. Tap on "All"
10. Open the report of the two workspace expenses.
11. Verify the new expense was created properly and is displayed on search section.

Expected Result:

The user should be able to create a new expense and send it to the same workspace of the just paid one, and this new expense should be displayed properly on "Search" section.

Actual Result:

When the user pay an expense via "Pay" button on expense preview on search, create another one and send it to the same workspace, an "Unexpected error" is displayed and the new expense is not created.
Issue can be reproduced only with Gmail accounts.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6662199_1731396212678.Unexpected.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @luacmartins

Issue Owner

Current Issue Owner: @luacmartins

[melvin-bot]

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

[joekaufmanexpensify]

I can't reproduce this on my gmail.com account. Works fine for me. I see the issue title says Android, but multiple platforms are selected, so I tested on web.

2024-11-12_10-32-39.mp4

[joekaufmanexpensify]

@Beamanator are you able to reproduce?