fix: missing pending indicator for bulk-edited expenses

[LukasMod]

Explanation of Change

src/libs/actions/IOU/index.ts — updateMultipleMoneyRequests():

• Snapshot optimistic data: Include pendingFields alongside updatedTransaction so the snapshot has pending state
• Snapshot success data (new): Add snapshotSuccessData array that clears pendingFields via clearedPendingFields when the API succeeds
• Snapshot failure data: Explicitly clear pendingFields via clearedPendingFields when reverting on failure (prevents stale pending state due to Onyx merge semantics)
• API call: Include snapshotSuccessData in the successData array passed to API.write()

src/libs/SearchUIUtils.ts:

• getTransactionsSections(): Derive pendingAction from pendingFields for transaction items in the individual Expenses search view
• getReportSections(): Same derivation for transactions inside the expense report grouped view
• Follows the existing pattern used for reports (line 2366: reportItem?.pendingAction ?? reportItem?.pendingFields?.preview)

Fixed Issues

$ #86842
$ #86841
PROPOSAL:

Tests

• Verify that no errors appear in the JS console

Test 1: Offline pending indicator

1. Go offline
2. Select 2+ expenses → "Edit multiple" → update merchant → Save
3. Verify: Expenses show updated merchant with faded/greyed-out appearance (50% opacity)
4. Go back online
5. Verify: Opacity clears after server confirms

Test 2: Failure revert

1. Simulate failed requests
2. Select 2+ expenses → "Edit multiple" → update merchant → Save
3. Verify: After failure, values revert to originals, no stuck pending indicator, error appears in transaction thread

Test 3: Slow network

1. Simulate poor internet
2. Select 2+ expenses → "Edit multiple" → update merchant → Save
3. Verify: Values update immediately with faded appearance while request is in-flight
4. Wait for request to complete
5. Verify: Opacity clears, values persist

Offline tests

QA Steps

• Verify that no errors appear in the JS console

Same as tests

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover 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 tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I verified there are no new alerts related to the canBeMissing param for useOnyx
• I followed proper code patterns (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
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • 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 followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• 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
• I verified that if a function's arguments changed that all usages have also been updated correctly
• 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 new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• 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.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user 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.

Screenshots/Videos

Screen.Recording.2026-04-02.at.14.52.11.mov

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

[codecov]

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/libs/SearchUIUtils.ts	66.32% <100.00%> (+0.09%)	⬆️
src/libs/actions/IOU/index.ts	78.59% <50.00%> (-0.07%)	⬇️
... and 14 files with indirect coverage changes

[melvin-bot]

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

[Krishna2323]

I’ll review this tomorrow morning (within 12 hours).

[Krishna2323]

I’ll review this tomorrow morning (within 12 hours).

Reviewing...🤦🏻

[Krishna2323]

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
  • MacOS: Desktop
• 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_hybrid.mp4

Android: mWeb Chrome

android_chrome.mp4

iOS: HybridApp

ios_hybrid.mp4

iOS: mWeb Safari

ios_safari.mp4

MacOS: Chrome / Safari

web_chrome_test_1.mp4

web_chrome_test_2.mp4

[Krishna2323]

LGTM! 🙇🏻

We have some conflicts to resolve.

[LukasMod]

Conflicts resolved

[Krishna2323]

@LukasMod please merge main. I’ve pinged @marcaaron on Slack to get this merged.

[LukasMod]

@Krishna2323 done ✅

[github-actions]

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

[github-actions]

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-3f797e0-f60c13a-b31c43d93e5f4211fd2b04d5d53f344ca55b736e/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-3f797e0-f60c13a-fcf6c4d35d4ad711364c52c433ea9ed2cf49334d/index.html

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

---

👀 View the workflow run that generated this build 👀

[OSBotify]

✋ 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]

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

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

Bundle Size Analysis (Sentry):

• Android

[MelvinBot]

No help site changes are required for this PR.

This is a bug fix that adds missing pending indicators (faded/greyed-out appearance) for bulk-edited expenses while offline requests are in-flight. The changes are internal to SearchUIUtils.ts and IOU/index.ts — no new features, workflows, settings, or UI labels were introduced. Existing help site articles remain accurate.

[IuliiaHerets]

Hi @LukasMod. QA team failed this PR with original issues: #86841 and #86842

1776138170214.ScreenRecording_04-13-2026_22-37-52_1.mp4

[Krishna2323]

Test 8: Optimistic updates and failure

1. Select 2+ expenses → "Edit multiple"
2. Update merchant to "NewMerchant" → Save
3. Verify expenses immediately show "NewMerchant" with pending indicators
4. After server confirms, verify pending indicators clear
5. (If possible) Simulate a failure

Verify:

• Expenses immediately show "NewMerchant" with pending indicators after save
• Pending indicators clear after server confirms
• On failure: expenses revert to original values and red error dot appears

@LukasMod the fix seems to be working but the Test 8 in the PR is a bit confusing. Can you please update that? We would also need to update the test steps in #86841 and #86842.

After Turn off Simulate failing network requests in #84756, the request is sent again and the expense shows the new merchant which is correct.

And in #86841, it needs to be tested in offline mode, not with Simulate failing network requests.

@IuliiaHerets could you please update the test steps in the original issues: #86841 and #86842?

[LukasMod]

@Krishna2323 Agree. Maybe we could replace Test 8 with tests I listed in this PR? WDYT?

Test 1: Offline pending indicator

1. Go offline
2. Select 2+ expenses → "Edit multiple" → update merchant → Save
3. Verify: Expenses show updated merchant with faded/greyed-out appearance (50% opacity)
4. Go back online
5. Verify: Opacity clears after server confirms

Test 2: Failure revert

1. Simulate failed requests
2. Select 2+ expenses → "Edit multiple" → update merchant → Save
3. Verify: After failure, values revert to originals, no stuck pending indicator, error appears in transaction thread

Test 3: Slow network

1. Simulate poor internet
2. Select 2+ expenses → "Edit multiple" → update merchant → Save
3. Verify: Values update immediately with faded appearance while request is in-flight
4. Wait for request to complete
5. Verify: Opacity clears, values persist

[Krishna2323]

Maybe we could replace Test 8 with tests I listed in this PR? WDYT?

Agree 👍 let’s replace Test 8 with those

[LukasMod]

@IuliiaHerets Could you check again please? Test 8 is updated. @Krishna2323 checked that fix is working for him so maybe there is no issue with this PR? I'm not sure what exactly is not working on attached video

[IuliiaHerets]

@LukasMod, according to the comment, Test 8a passes. However, in Test 8b, values changed during a poor connection are not displayed with a faded appearance

ScreenRecording_04-14-2026.10-50-17_1.mp4

[OSBotify]

🚀 Deployed to production by https://github.com/AndrewGable in version: 9.3.59-4 🚀

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

[LukasMod]

@IuliiaHerets I rechecked and it seems like its by design. The "Simulate poor internet connection" toggle randomly flips isOffline between true and false every 2-5 seconds. The faded appearance comes from OfflineWithFeedback, which only applies opacity when isOffline is true.

This means Test 8b produces two different outcomes depending on timing:

• Save during a random "offline" flip → request queued, fading shows → same as Test 9: Offline bulk edit, case from my video
• Save during a random "online" flip → request completes immediately, no fading visible <<<< case from your video

The test doesn't verify any unique behavior, it's just the offline test with a coin flip. If fading shows, it's because the app happened to be offline. If it doesn't, it's because the app happened to be online. I think we could remove test 8b from that list