fix: Unable to basic export expense when in group-by view by truph01 · Pull Request #80969 · Expensify/App

truph01 · 2026-01-30T00:50:48Z

Explanation of Change

In the test case described in [Due for payment 2026-02-26] [$250] Reports - Unable to basic export expense when in group-by view #79194, the export feature works correctly after the backend fix. However, there is still an issue: the reportIDList sent to the backend via the ExportSearchToCSV API is always empty. This PR ensures that the correct reportIDList data is sent to the backend.

Fixed Issues

$ #79194
PROPOSAL: #79194 (comment)

Tests

Go to staging.new.expensify.com
Go to workspace chat.
Create an expense.
Go to Reports > Expenses.
Click Filters.
Click Group by > select From.
Click Save > View results.
Expand the row.
Select the expense via checkbox.
Click dropdown button > Export > Basic export.
Verify: The expense can be exported when in group-by result.

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]."

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Screen.Recording.2026-02-10.at.15.02.03.mov

Android: mWeb Chrome

Screen.Recording.2026-02-10.at.14.55.30.mov

iOS: Native

Screen.Recording.2026-02-10.at.14.57.07.mov

iOS: mWeb Safari

Screen.Recording.2026-02-10.at.14.53.22.mov

MacOS: Chrome / Safari

Screen.Recording.2026-02-10.at.14.49.40.mov

codecov · 2026-02-10T07:55:07Z

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
src/pages/Search/SearchPage.tsx	`22.74% <0.00%> (ø)`
... and 13 files with indirect coverage changes

melvin-bot · 2026-02-10T08:06:21Z

@hoangzinh 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]

github-actions · 2026-02-10T08:08:26Z

src/pages/Search/SearchPage.tsx

                query: status,
                jsonQuery: JSON.stringify(queryJSON),
-                reportIDList: selectedReports?.map((report) => report?.reportID).filter((reportID) => reportID !== undefined) ?? [],
+                reportIDList:


❌ CONSISTENCY-3 (docs)

This code duplicates logic already computed in selectedReportIDs (lines 184-186) and selectedTransactionReportIDs (lines 174-183). Re-computing these values increases maintenance overhead and creates inconsistency.

Suggested fix:

reportIDList: selectedReports.length > 0 ? selectedReportIDs : selectedTransactionReportIDs,

This reuses the already-computed, memoized values instead of duplicating the extraction logic.

Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

It looks correct to me. Wdyt?

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 94ba1a21bf

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector · 2026-02-10T08:13:31Z

src/pages/Search/SearchPage.tsx

+                        : (Object.values(selectedTransactions ?? {})
+                              .map((transaction) => transaction?.reportID)
+                              ?.filter((reportID) => reportID !== undefined) ?? []),


Add selectedTransactions to basic export callback deps

This new fallback reads selectedTransactions to build reportIDList, but handleBasicExport’s useCallback dependency array was not updated to include selectedTransactions. In grouped views, selection metadata can be refreshed while the selected key set stays the same (so selectedTransactionsKeys does not change), which leaves this callback closing over stale transaction objects and can send outdated or empty reportIDList values to exportSearchItemsToCSV.

Useful? React with 👍 / 👎.

hoangzinh · 2026-02-10T10:34:16Z

@truph01 I have a feedback here #80969 (comment)

JmillsExpensify

Part of an existing product initiative.

hoangzinh · 2026-02-16T23:18:04Z

@truph01 I have a feedback here #80969 (comment)

How is it going? @truph01

truph01 · 2026-02-17T01:33:56Z

@hoangzinh I just applied your suggestion.

hoangzinh · 2026-02-18T01:06:06Z

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

Screen.Recording.2026-02-18.at.08.10.12.mov

Android: mWeb Chrome

Screen.Recording.2026-02-18.at.08.07.58.mov

iOS: HybridApp

Screen.Recording.2026-02-18.at.08.11.52.mov

iOS: mWeb Safari

Screen.Recording.2026-02-18.at.08.13.29.mov

MacOS: Chrome / Safari

Screen.Recording.2026-02-18.at.08.04.57.mov

hoangzinh

LGTM 🙏

github-actions · 2026-02-18T13:14:54Z

🚧 @mjasikowski has triggered a test Expensify/App build. You can view the workflow run here.

github-actions · 2026-02-18T13:18:43Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #80969.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-2cc066f-09da3e9-c7cedcd42615fe0f172530c4196b53e700065ef1/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-2cc066f-09da3e9-36afbb556ceb441739af345b5fc7da8f7c812697/index.html

Web 🕸️
https://80969.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

OSBotify · 2026-02-18T13:22:02Z

✋ 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-18T22:20:13Z

🚀 Deployed to staging by https://github.com/mjasikowski in version: 9.3.22-0 🚀

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

OSBotify · 2026-02-19T17:21:03Z

🚀 Deployed to production by https://github.com/mountiny in version: 9.3.22-4 🚀

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

OSBotify · 2026-02-19T17:35:23Z

🚀 Deployed to production by https://github.com/mountiny in version: 9.3.22-4 🚀

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

fix: Unable to basic export expense when in group-by view

a05c257

melvin-bot bot assigned truph01 Jan 30, 2026

truph01 added 2 commits February 10, 2026 14:30

Merge branch 'Expensify:main' into fix/79194

7f8211a

fix: lint

94ba1a2

truph01 marked this pull request as ready for review February 10, 2026 08:06

truph01 requested review from a team as code owners February 10, 2026 08:06

melvin-bot bot requested a review from hoangzinh February 10, 2026 08:06

melvin-bot bot requested review from JmillsExpensify and removed request for a team February 10, 2026 08:06

github-actions bot reviewed Feb 10, 2026

View reviewed changes

chatgpt-codex-connector bot reviewed Feb 10, 2026

View reviewed changes

hoangzinh mentioned this pull request Feb 10, 2026

[Due for payment 2026-02-26] [$250] Reports - Unable to basic export expense when in group-by view #79194

Closed

7 tasks

JmillsExpensify previously approved these changes Feb 13, 2026

View reviewed changes

truph01 added 2 commits February 17, 2026 08:24

Merge branch 'Expensify:main' into fix/79194

9709d1a

fix: apply bot's comment

f4a4b6e

truph01 dismissed JmillsExpensify’s stale review via f4a4b6e February 17, 2026 01:30

hoangzinh approved these changes Feb 18, 2026

View reviewed changes

melvin-bot bot requested a review from mjasikowski February 18, 2026 01:56

mjasikowski approved these changes Feb 18, 2026

View reviewed changes

mjasikowski merged commit 2cc066f into Expensify:main Feb 18, 2026
31 of 32 checks passed

OSBotify mentioned this pull request Feb 18, 2026

Deploy Checklist: New Expensify 2026-02-18 #82863

Closed

76 tasks

Conversation

truph01 commented Jan 30, 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!

codecov bot commented Feb 10, 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!

melvin-bot bot commented Feb 10, 2026

Uh oh!

github-actions bot Feb 10, 2026

Choose a reason for hiding this comment

❌ CONSISTENCY-3 (docs)

Uh oh!

hoangzinh Feb 10, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector bot Feb 10, 2026

Choose a reason for hiding this comment

Uh oh!

hoangzinh commented Feb 10, 2026

Uh oh!

JmillsExpensify left a comment

Choose a reason for hiding this comment

Uh oh!

hoangzinh commented Feb 16, 2026

Uh oh!

truph01 commented Feb 17, 2026

Uh oh!

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

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

hoangzinh left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actions bot commented Feb 18, 2026

Uh oh!

github-actions bot commented Feb 18, 2026

Uh oh!

OSBotify commented Feb 18, 2026

Uh oh!

OSBotify commented Feb 18, 2026

Uh oh!

OSBotify commented Feb 19, 2026

Uh oh!

OSBotify commented Feb 19, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

truph01 commented Jan 30, 2026 •

edited

Loading

codecov bot commented Feb 10, 2026 •

edited by github-actions bot

Loading

hoangzinh commented Feb 18, 2026 •

edited

Loading