[Due for payment 2025-07-15] [$250] Reports - App background changes to Inbox after opening report details page on Reports page

[mitarachim]

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.71-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp https://expensify.testrail.io/index.php?/tests/view/6353911
Email or phone of affected tester (no customers): dsnsjdoiiojsodj3o@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Submit two expenses to the workspace chat.
4. Go to Reports > Expenses.
5. Open any expense.
6. Close the RHP.
7. Go to Reports > Reports.
8. Click View on any expense row.
9. Click the arrow next button.
10. Click on the header avatar.

Expected Result:

App background will remain in Reports page.

Actual Result:

App background changes to Inbox after opening report details page on Reports page.

On small screen, LHN opens.

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

Bug6869216_1750833332071.20250625_143441.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021937838807694712513
• Upwork Job ID: 1937838807694712513
• Last Price Increase: 2025-06-25

Issue Owner

Current Issue Owner: @twisterdotcom

[melvin-bot]

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

[Eskalifer1]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Reports - App background changes to Inbox after opening report details page on Reports page

What is the root cause of that problem?

The main problem is in this component, namely in this line:

App/src/components/MoneyRequestReportView/MoneyRequestReportTransactionsNavigation.tsx

Line 35 in 67e472c

const backTo = Navigation.getActiveRoute();

The situation is as follows: The component saves the value it received during rendering, even if the value has changed

And the initial value is as follows: initial=true&screen=SearchReport&params=%5Bobject%20Object%5D

Accordingly, when you press the backTo button, it will be set to this value, as a result of which the screen behind will change

What changes do you think we should make in order to solve the problem?

The simplest solution is to add this line

 const backTo = Navigation.getActiveRoute();

directly to the onNext and onPrevious functions, that is, it will look like this:

onNext={(e) => {
 const backTo = Navigation.getActiveRoute();
 e?.preventDefault();
 Navigation.navigate(ROUTES.SEARCH_REPORT.getRoute({reportID: nextReportID, backTo}), {forceReplace: true});
 }}
 onPrevious={(e) => {
 const backTo = Navigation. getActiveRoute();
 e?.preventDefault();
 Navigation.navigate(ROUTES.SEARCH_REPORT.getRoute({reportID: prevReportID, backTo}), {forceReplace: true});
 }}

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

None

What alternative solutions did you explore? (Optional)

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[twisterdotcom]

I can't recreate this.