fix: empty state screen displayed after approving or paying expense by daledah · Pull Request #81376 · Expensify/App

daledah · 2026-02-04T07:07:56Z

Explanation of Change

Fixed Issues

$ #80424
PROPOSAL: #80424 (comment)

Tests

Prerequisites:

Account has at least one workspace.
Delayed submissions and approvals enabled.
No expenses exist before

Open the Expensify app.
Open any workspace chat.
Create a manual expense.
Navigate to "Reports" > "Expenses"
Tap on "Submit" on preview of the just created expense.
Tap on "Approve"
Note that empty state screen is shown for a few seconds after this action.
Mark the expense as paid.
Verify that: After approving or paying an expense while on "Expenses" section on "Reports", preview of the expense should remain visible and status should change.

Verify that no errors appear in the JS console

Offline tests

Same as tests

QA Steps

Same as tests

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

Screen.Recording.2026-03-02.at.22.54.19.mov

codecov · 2026-02-04T07:17:22Z

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 Δ
src/components/Search/index.tsx	`34.45% <0.00%> (-0.07%)`	⬇️
... and 14 files with indirect coverage changes

melvin-bot · 2026-03-02T15:55:07Z

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

daledah · 2026-03-02T15:55:19Z

Oopen the PR for review, i'll add the missing records soon

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: cafc795c0c

ℹ️ 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-03-02T16:01:39Z

src/components/Search/index.tsx

+    const isAnyActionLoading = isActionLoadingSet.size > 0;
    const visibleDataLength = filteredData.filter((item) => item.pendingAction !== CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE || isOffline).length;
-    if (shouldShowEmptyState(isDataLoaded, visibleDataLength, searchDataType)) {
+    if (shouldShowEmptyState(isDataLoaded, visibleDataLength, searchDataType) && !isAnyActionLoading) {


Limit empty-state suppression to visible loading reports

isAnyActionLoading is derived from isActionLoadingSet.size > 0, but useActionLoadingReportIDs() collects loading flags for all reports in Onyx, not just the current search results. This means EmptySearchView is hidden whenever any unrelated report action is pending, so an actually empty search can render a blank list with no empty-state message until that other action finishes. The guard should be scoped to loading items present in the current filteredData/search hash rather than global loading state.

Useful? React with 👍 / 👎.

@daledah Could you verify this bot comment? Thanks

@hungvu193 i updated

hungvu193 · 2026-03-08T08:12:04Z

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 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-03-08.at.15.35.04.mov

Android: mWeb Chrome

Screen.Recording.2026-03-08.at.15.36.27.mov

iOS: HybridApp

Screen.Recording.2026-03-08.at.15.29.56.mov

iOS: mWeb Safari

Screen.Recording.2026-03-08.at.15.22.56.mov

MacOS: Chrome / Safari

Screen.Recording.2026-03-08.at.15.07.58.mov

github-actions · 2026-03-09T13:20:24Z

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

github-actions · 2026-03-09T13:24:42Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-50f33be-b9c28a3-f428a5a5f59aa0b49417b7702ab39c96b74d84a2/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-50f33be-b9c28a3-c0d4556c6ed7853514f602451bf3f0e803b9be52/index.html

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

👀 View the workflow run that generated this build 👀

OSBotify · 2026-03-09T15:57:17Z

✋ 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-03-09T21:26:13Z

🚀 Deployed to staging by https://github.com/Valforte in version: 9.3.34-0 🚀

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

OSBotify · 2026-03-10T18:48:19Z

🚀 Deployed to production by https://github.com/luacmartins in version: 9.3.34-2 🚀

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

fix: empty state screen displayed after approving or paying expense

9a2d0b6

melvin-bot bot assigned daledah Feb 4, 2026

Merge branch 'main' into fix/80424

fc07485

daledah mentioned this pull request Feb 6, 2026

[Due for payment 2026-03-17] [$250] Reports - Empty state screen displayed after approving or paying expense. #80424

Closed

7 tasks

resolve conflict

cafc795

daledah marked this pull request as ready for review March 2, 2026 15:54

daledah requested review from a team as code owners March 2, 2026 15:54

melvin-bot bot requested review from heyjennahay and hungvu193 and removed request for a team March 2, 2026 15:55

chatgpt-codex-connector bot reviewed Mar 2, 2026

View reviewed changes

daledah added 2 commits March 5, 2026 16:03

Merge branch 'main' into fix/80424

49b038f

fix bot comments

ef66f57

hungvu193 approved these changes Mar 8, 2026

View reviewed changes

melvin-bot bot requested a review from Valforte March 8, 2026 08:37

Valforte approved these changes Mar 9, 2026

View reviewed changes

Valforte merged commit 50f33be into Expensify:main Mar 9, 2026
30 of 31 checks passed

github-actions bot mentioned this pull request Mar 9, 2026

Investigate workflow job failing on main: test / test (job 8) #84593

Closed

OSBotify mentioned this pull request Mar 9, 2026

Deploy Checklist: New Expensify 2026-03-09 #84634

Closed

75 tasks

Conversation

daledah commented Feb 4, 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 4, 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 Mar 2, 2026

Uh oh!

daledah commented Mar 2, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector bot Mar 2, 2026

Choose a reason for hiding this comment

Uh oh!

hungvu193 Mar 4, 2026

Choose a reason for hiding this comment

Uh oh!

daledah Mar 5, 2026

Choose a reason for hiding this comment

Uh oh!

hungvu193 commented Mar 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

Uh oh!

github-actions bot commented Mar 9, 2026

Uh oh!

github-actions bot commented Mar 9, 2026

Uh oh!

OSBotify commented Mar 9, 2026

Uh oh!

OSBotify commented Mar 9, 2026

Uh oh!

OSBotify commented Mar 10, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

daledah commented Feb 4, 2026 •

edited

Loading

codecov bot commented Feb 4, 2026 •

edited by github-actions bot

Loading

hungvu193 commented Mar 8, 2026 •

edited

Loading