Fix: Cannot navigate duplicated expenses via arrow keys by cretadn22 · Pull Request #80224 · Expensify/App

cretadn22 · 2026-01-22T13:27:08Z

Explanation of Change

Fixed Issues

$ #77286
PROPOSAL: #77286 (comment)

Tests

The first bug

Go to staging.new.expensify.com
Go to workspace chat.
Create two expenses.
Open the expense report.
Open any expense.
Click More > Duplicate.
Use arrows on the top right to navigate to the duplicated expense.
Duplicated expense can be navigated via arrows.

The regression bug

Go to staging.new.expensify.com
Go to workspace chat.
Create two expenses.
Go to Reports > Expenses.
Open any expense.
Click on the header subtitle to open expense report.
Click RHP back button.
Navigation arrows should remain hidden after returning from expense report.

Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

Go to staging.new.expensify.com
Go to workspace chat.
Create two expenses.
Open the expense report.
Open any expense.
Click More > Duplicate.
Use arrows on the top right to navigate to the duplicated expense.
Duplicated expense can be navigated via arrows.

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Screen.Recording.2026-01-06.at.18.58.14.mov

Screen.Recording.2026-01-22.at.20.50.14.mov

Android: mWeb Chrome

Screen.Recording.2026-01-22.at.20.51.39.mov

Screen.Recording.2026-01-22.at.20.51.12.mov

iOS: Native

Screen.Recording.2026-01-22.at.20.47.39.mov

Screen.Recording.2026-01-22.at.20.47.12.mov

iOS: mWeb Safari

Screen.Recording.2026-01-06.at.18.54.26.mov

Screen.Recording.2026-01-22.at.20.49.04.mov

MacOS: Chrome / Safari

Screen.Recording.2026-01-22.at.20.45.56.mov

Screen.Recording.2026-01-22.at.20.46.14.mov

…d useDeepCompareRef, update active transaction IDs based on focused route

melvin-bot · 2026-01-22T13:27:15Z

@jjcoffee Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

src/components/MoneyRequestReportView/MoneyRequestReportTransactionList.tsx

…declaration into useEffect for better clarity

codecov · 2026-01-22T13:43:11Z

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines	Coverage Δ
...stReportView/MoneyRequestReportTransactionList.tsx	`1.29% <0.00%> (-0.05%)`	⬇️
... and 6 files with indirect coverage changes

…IDs on unmount

cretadn22 · 2026-01-22T13:45:13Z

src/components/MoneyRequestReportView/MoneyRequestReportTransactionList.tsx

        return groupedTransactions.flatMap((group) => group.transactions.filter((transaction) => !isTransactionPendingDelete(transaction)).map((transaction) => transaction.transactionID));
    }, [groupedTransactions, sortedTransactions, shouldShowGroupedTransactions]);

+    const visualOrderTransactionIDsDeepCompare = useDeepCompareRef(visualOrderTransactionIDs);


On mobile web, useEffect is still triggered while the component is in the process of unmounting. To address the regression on mobile web, we have to use useDeepCompareRef.

cretadn22 · 2026-01-27T12:00:18Z

@jjcoffee Any chance you could review this new PR?

jjcoffee · 2026-01-29T10:34:58Z

@cretadn22 Sorry I'm off sick at the moment. Are you able to sort out the coverage in the meantime?

…-compare

…ReportTransactionListActiveTransactionIDsTest

cretadn22 · 2026-01-29T11:50:12Z

@jjcoffee I added tests

jjcoffee · 2026-02-02T12:51:57Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified there are no new alerts related to the canBeMissing param for useOnyx
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

android-app-2026-02-02_14.21.30.mp4

Android: mWeb Chrome

android-chrome-2026-02-02_14.24.46.mp4

iOS: HybridApp

ios-app-2026-02-02_13.57.36.mp4

iOS: mWeb Safari

ios-safari-2026-02-02_14.00.16.mp4

MacOS: Chrome / Safari

desktop-chrome-2026-02-02_13.45.51.mp4

jjcoffee

LGTM! Sorry for the delay 🙇

OSBotify · 2026-02-02T13:54:29Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2026-02-03T02:14:29Z

🚀 Deployed to staging by https://github.com/JS00001 in version: 9.3.11-19 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	cancelled 🔪
🍎 iOS 🍎	cancelled 🔪

OSBotify · 2026-02-05T20:19:41Z

🚀 Deployed to production by https://github.com/Julesssss in version: 9.3.12-1 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	failure ❌

Enhance MoneyRequestReportTransactionList: Import findFocusedRoute an…

8b7b4e6

…d useDeepCompareRef, update active transaction IDs based on focused route

cretadn22 requested review from a team as code owners January 22, 2026 13:27

melvin-bot bot assigned cretadn22 Jan 22, 2026

melvin-bot bot requested review from JmillsExpensify and jjcoffee and removed request for a team and JmillsExpensify January 22, 2026 13:27

melvin-bot bot removed the request for review from a team January 22, 2026 13:27

github-actions bot reviewed Jan 22, 2026

View reviewed changes

src/components/MoneyRequestReportView/MoneyRequestReportTransactionList.tsx Outdated Show resolved Hide resolved

github-actions bot reviewed Jan 22, 2026

View reviewed changes

src/components/MoneyRequestReportView/MoneyRequestReportTransactionList.tsx Show resolved Hide resolved

Remove unused clearActiveTransactionIDs import and move focusedRoute …

e5cc52f

…declaration into useEffect for better clarity

Update MoneyRequestReportTransactionList to clear active transaction …

8e3f457

…IDs on unmount

cretadn22 commented Jan 22, 2026

View reviewed changes

cretadn22 added 3 commits January 29, 2026 17:40

Merge branch 'main' into use-setActiveTransactionIDs-dynamically-deep…

cb6e576

…-compare

add MoneyRequestReportTransactionListActiveTransactionIDsTest

3341180

Refactor test setup to use jest.Mock for getRootState in MoneyRequest…

c90d2b7

…ReportTransactionListActiveTransactionIDsTest

jjcoffee approved these changes Feb 2, 2026

View reviewed changes

melvin-bot bot requested a review from JS00001 February 2, 2026 13:26

JS00001 approved these changes Feb 2, 2026

View reviewed changes

JS00001 merged commit 199a23f into Expensify:main Feb 2, 2026
30 checks passed

OSBotify mentioned this pull request Feb 3, 2026

Deploy Checklist: New Expensify 2026-01-28 #80808

Closed

jponikarchuk mentioned this pull request Feb 3, 2026

Expense - Duplicated expense auto moved to different workspace #81298

Closed

7 tasks

jjcoffee mentioned this pull request Feb 11, 2026

[$250] Expense - Duplicated expense cannot be navigated via arrows #77286

Closed

8 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix: Cannot navigate duplicated expenses via arrow keys#80224

Fix: Cannot navigate duplicated expenses via arrow keys#80224
JS00001 merged 6 commits intoExpensify:mainfrom
cretadn22:use-setActiveTransactionIDs-dynamically-deep-compare

cretadn22 commented Jan 22, 2026 •

edited

Loading

Uh oh!

melvin-bot bot commented Jan 22, 2026

Uh oh!

Uh oh!

Uh oh!

codecov bot commented Jan 22, 2026 •

edited by github-actions bot

Loading

Uh oh!

cretadn22 Jan 22, 2026

Uh oh!

cretadn22 commented Jan 27, 2026

Uh oh!

jjcoffee commented Jan 29, 2026

Uh oh!

cretadn22 commented Jan 29, 2026

Uh oh!

jjcoffee commented Feb 2, 2026 •

edited

Loading

Uh oh!

jjcoffee left a comment

Uh oh!

Uh oh!

OSBotify commented Feb 2, 2026

Uh oh!

OSBotify commented Feb 3, 2026

Uh oh!

OSBotify commented Feb 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

cretadn22 commented Jan 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Jan 22, 2026

Uh oh!

Uh oh!

Uh oh!

codecov bot commented Jan 22, 2026 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

cretadn22 Jan 22, 2026

Choose a reason for hiding this comment

Uh oh!

cretadn22 commented Jan 27, 2026

Uh oh!

jjcoffee commented Jan 29, 2026

Uh oh!

cretadn22 commented Jan 29, 2026

Uh oh!

jjcoffee commented Feb 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

jjcoffee left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

OSBotify commented Feb 2, 2026

Uh oh!

OSBotify commented Feb 3, 2026

Uh oh!

OSBotify commented Feb 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

cretadn22 commented Jan 22, 2026 •

edited

Loading

codecov bot commented Jan 22, 2026 •

edited by github-actions bot

Loading

jjcoffee commented Feb 2, 2026 •

edited

Loading