[Due for payment 2025-06-23] [Due for payment 2025-06-09] [Due for payment 2025-06-05] Reports - Current report is not added to other selected report after submitting transaction

[nlemma]

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.1.53-2
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #62659
Email or phone of affected tester (no customers): applausetester+ck528251@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: iPhone 16/iOS 18.3.1
App Component: Money Requests

Action Performed:

Precondition:
Log in with Expensifail account
A workspace
Account has no outstanding (un-submitted) expense report

1. Launch Hybrid app
2. + > Create report
3. + > Create expense
4. Enter amount, tap Show more
5. Verify that the Report field is not editable
6. Submit the expense
7. + > Create report
8. + > Create expense
9. Enter amount, tap Show more
10. Verify that the Report field is editable
11. Select the report field
12. Verify that you see both reports and the current report is selected
13. Select the other report
14. Submit the transaction

Expected Result:

Current report is added to other selected report when submitting transaction

Actual Result:

Current report is not added to other selected report after submitting transaction. After creating expense, the report field is reset to the second report & not added to the first selected one

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

Bug6844572_1748444021448.ScreenRecording_05-28-2025_10-50-45_1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @muttmuure

[melvin-bot]

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

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

[nlemma]

@muttmuure 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.