Repository navigation
Description
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.2.34-2
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-1375/41236824/962798590?q=merge&issue_type=jira
Email or phone of affected tester (no customers): ibellicotest+1934@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb / Hybrid app) - Windows 11 / Chrome
App Component: Search
Action Performed:
Prerequisite: Account has at least one workspace.
- Open the Expensify app.
- Open any workspace chat.
- Create two manual expenses on two different reports.
- Navigate to "Reports"
- Open any of the just created expenses.
- Tap on "More" and select "Merge"
- Keep all the details of the expense that wasn´t opened.
- Note that after finishing the merging process, you land on chat instead of returning to "Reports".
- Tap on the arrow on the top left corner.
- Note that you land on "Inbox" instead of returning to "Reports"
Expected Result:
After merging expenses on "Reports", user should land on the same section.
Actual Result:
After merging expenses on "Reports", user lands on chat instead of returning to the same section. Also, tapping on the back button on chat, leads to "Inbox" instead of returning to "Reports".
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
1.mp4
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021983654416053240372
- Upwork Job ID: 1983654416053240372
- Last Price Increase: 2025-10-29
Issue Owner
Current Issue Owner: @heyjennahayMetadata
Metadata
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
melvin-bot commentedon Oct 21, 2025
Triggered auto assignment to @heyjennahay (
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.paulnjs commentedon Oct 21, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
After merging expenses on "Reports", user lands on chat instead of returning to the same section. Also, tapping on the back button on chat, leads to "Inbox" instead of returning to "Reports".
What is the root cause of that problem?
We always navigate to the report screen after merging expenses.
App/src/pages/TransactionMerge/ConfirmationPage.tsx
Line 81 in f9ee4f0
What changes do you think we should make in order to solve the problem?
If we're on
Reportswe should navigate to search money report screen insteadApp/src/pages/TransactionMerge/ConfirmationPage.tsx
Line 81 in f9ee4f0
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
undefined
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.
abzokhattab commentedon Oct 21, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
After merging expenses from the Reports section, users are redirected to chat instead of returning to Reports, and the back button leads to Inbox.
What is the root cause of that problem?
backToparameter (which contains the route back to Reports) is available in the route params but is not being passed toNavigation.dismissModalWithReport()backToparameter, the navigation system doesn't know where the user came from, so it defaults to navigating to the chat without the proper navigation contextWhat changes do you think we should make in order to solve the problem?
add back to param to
dismissModalWithReporthereThis ensures the it knows to return to the Reports page after the merge operation completes.
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
NA
What alternative solutions did you explore? (Optional)
NA
ShridharGoel commentedon Oct 21, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
After merging two expenses from the Reports section, the app sends the user back to the chat view and then to the Inbox when they press back. We want the flow to return the user to the same Reports section they started from.
What is the root cause of that problem?
The confirmation screen simply dismisses the merge modal
App/src/pages/TransactionMerge/ConfirmationPage.tsx
Lines 70 to 101 in a97e742
so navigation falls back to the chat route instead of the section captured in
backTo.What changes do you think we should make in order to solve the problem?
backTovalue that the flow carried forward, and navigate to it once the merge is confirmed.backTovalue is present, so other merge entry points keep working.dmkt9 commentedon Oct 21, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
After merging expenses on "Reports", user lands on chat instead of returning to the same section. Also, tapping on the back button on chat, leads to "Inbox" instead of returning to "Reports".
What is the root cause of that problem?
Since the target reportID is different from the current reportID, it will trigger
Navigation.dismissModalWithReportto dismiss the modal and navigate to the target report:App/src/pages/TransactionMerge/ConfirmationPage.tsx
Line 81 in d1ad27d
However, inside
Navigation.dismissModalWithReport, it only navigates toROUTES.REPORT_WITH_ID.What changes do you think we should make in order to solve the problem?
In
dismissModalWithReport, we should check whether we're currently on the search screen. If so, navigate toROUTES.SEARCH_MONEY_REQUEST_REPORTinstead.App/src/libs/Navigation/Navigation.ts
Line 574 in d1ad27d
melvin-bot commentedon Oct 28, 2025
@heyjennahay 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
melvin-bot commentedon Oct 29, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021983654416053240372
[-]Reports - User is redirected to chat after merging expenses on "Reports"[/-][+][$250] Reports - User is redirected to chat after merging expenses on "Reports"[/+]49 remaining items
heyjennahay commentedon Jan 13, 2026
Payment summary
heyjennahay commentedon Jan 13, 2026
Also @paulnjs for future reference, can you please keep an eye out for this post for you to action when your proposal is accepted so the offer can be sent from the original job posting in Upwork? #73057 (comment)
paulnjs commentedon Jan 13, 2026
@heyjennahay noted that. Thanks for reminding me 🙏
heyjennahay commentedon Jan 13, 2026
Sorry @paulnjs I added the wrong link for the offer. Here it is https://www.upwork.com/nx/wm/offer/110091078
heyjennahay commentedon Jan 14, 2026
@paulnjs paid $250 via Upwork. Confirmed that the contract has been closed.
Thanks everyone!
paulnjs commentedon Jan 14, 2026
Hi @heyjennahay, could you please help to check why this is not woking for me even though I applied many jobs before?
heyjennahay commentedon Jan 14, 2026
@paulnjs to clarify, you have clicked on one of the job links like here to get an offer sent to you that way? #73057 (comment)
mallenexpensify commentedon Jan 14, 2026
👋 Jobs auto-close after one month :/
My guess is, after this post, you didn't apply @paulnjs , so the job closed.
I created a new Upwork job here @paulnjs , please apply and tag @heyjennahay and I in a comment here once you have. Thx
paulnjs commentedon Jan 15, 2026
@heyjennahay Yes, many times before on previous issues
@mallenexpensify For this one, I was already paid by @heyjennahay
We're all good here, thanks!
mallenexpensify commentedon Jan 16, 2026
Thanks @paulnjs
melvin-bot commentedon Feb 5, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
parasharrajat commentedon Mar 19, 2026
Payment requested as per #73057 (comment)
twisterdotcom commentedon Mar 19, 2026
@parasharrajat has submitted payment for this report on ND here.
SO: https://stackoverflowteams.com/c/expensify/questions/7582
Zapier Logs
Run ID: 00040eee-5d6e-aa92-9d5e-705c9c2db054