Reapply "Reapply "Feat: bulk edit multiple""

[pasyukevich]

This reverts commit 75e65f3.

Explanation of Change

Fixed Issues

$ #75617
PROPOSAL:

Tests

---

Enabling bulkEdit Beta for Developers

Edit src/libs/Permissions.ts

Add a temporary early-return inside isBetaEnabled:

function isBetaEnabled(beta: Beta, betas: OnyxEntry<Beta[]>, betaConfiguration?: OnyxEntry<BetaConfiguration>): boolean {
    // DEV ONLY — remove before merging
    // eslint-disable-next-line rulesdir/no-beta-handler
    if (beta === CONST.BETAS.BULK_EDIT) {
        return true;
    }

    const hasAllBetasEnabled = canUseAllBetas(betas);
    // ... rest unchanged

OR add bulkEdit to your account's beta list

Bulk Edit Expenses — Test Cases

---

Test 1: Basic bulk edit from Search page

1. Create 3+ expenses on the same workspace
2. Go to Search → Expenses tab
3. Select all 3 expenses
4. Press "Edit multiple"
5. Update merchant to "Starbucks", pick a category, pick a date
6. Press Save

Verify:

• All 3 expenses show updated merchant, category, and date
• Open one expense's transaction thread → verify system message shows old → new values

---

Test 2: Basic bulk edit from Report page

1. Open a report with 3+ editable expenses
2. Select 2+ expenses using checkboxes
3. Press "Edit multiple"
4. Update description to "Team lunch"
5. Press Save

Verify:

• All selected expenses show "Team lunch" as description

---

Test 3: Cross-policy bulk edit

1. Create 2 expenses on Workspace A and 2 on Workspace B
2. Go to Search → select all 4 expenses
3. Press "Edit multiple"
4. Pick a category from the active workspace's list
5. Press Save

Verify:

• Category applied to all expenses
• Transactions on the other workspace may show a violation — that's expected

---

Test 4: Multi-level/dependent tags

1. Set up a workspace with tags (e.g., Region → City)
2. Create 2+ expenses on that workspace
3. Select them → "Edit multiple"
4. Select parent tag (e.g., "US")
5. Verify child tag level (e.g., "City") appears on the edit page
6. Select child tag (e.g., "New York")
7. Press Save

Verify:

• Both tag levels saved correctly on expenses

---

Test 5: Non-editable fields silently skipped

1. Create 2 regular expenses and 1 distance request
2. Select all 3 → "Edit multiple"
3. Verify Amount and Merchant fields are disabled (greyed out, no right caret)
4. Update category → Save

Verify:

• Category updated on all 3 expenses
• Amount and merchant remain unchanged

---

Test 6: Unchanged fields not sent

1. Create 3 expenses all with merchant "Uber"
2. Select all 3 → "Edit multiple"
3. Set merchant to "Uber" (same value) and category to "Travel"
4. Press Save

Verify:

• Only category changed on the expenses
• Merchant stays unchanged
• No unnecessary pending indicators on merchant

---

Test 7: Save with no edits

1. Select 2+ expenses → "Edit multiple"
2. Don't edit any field
3. Press Save

Verify:

• RHP dismisses
• No API calls
• Nothing changes on any expense

---

Test 8: Optimistic updates and failure

Test 8a: Failure revert

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

Test 8b: 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

---

Test 9: Offline bulk edit

1. Go offline
2. Select 2+ expenses → "Edit multiple"
3. Update a field → Save
4. Verify expenses show as greyed out (50% opacity)
5. Go back online

Verify:

• Expenses show as greyed out (50% opacity) while offline
• Updates sync and greyed-out state clears after coming back online

---

Test 10: Sub-pages show correct policy options from Search page

Setup:

• Workspace A (active) with categories: Food, Travel
• Workspace B with categories: Engineering, Marketing

1. Create 2 expenses on Workspace B
2. Go to Search → select both expenses → "Edit multiple"
3. Tap Category

Verify:

• Category picker shows Workspace B's categories (Engineering, Marketing), not Workspace A's

---

Test 11: Approved/paid expenses excluded

1. Have 2 editable expenses and 1 expense from an approved report
2. Select all 3 on Search page

Verify:

• "Edit multiple" is hidden (current behavior)

---

Test 12: Tax rate bulk edit

1. Set up a workspace with tax tracking enabled
2. Create 2+ expenses
3. Select them → "Edit multiple"
4. Tap Tax Rate → select a rate → Save

Verify:

• Tax rate updated on all expenses

---

Test 13: Billable / Reimbursable toggle

1. Set up a workspace with billable field enabled
2. Create 2+ expenses
3. Select them → "Edit multiple"
4. Tap Billable → select "Yes" → go back
5. Tap Reimbursable → select "No" → go back
6. Press Save

Verify:

• Billable and reimbursable flags updated correctly on all expenses

---

Test 14: Merchant preview not updated after offline bulk edit

Precondition: Account has at least one workspace.

1. Open the Expensify app
2. Open any workspace chat
3. Create a manual expense
4. Navigate to Reports → Expenses
5. Turn off internet connection
6. Create a new manual expense via FAB with different merchant and category
7. Select both expenses
8. Tap on dropdown menu and select "Edit Multiple"
9. Add new merchant, category and description to expenses and save

Expected Result:
After multiple editing expenses while offline, all the edited fields should automatically update on preview and inside report.

---

Test 15: Description not saved when using "Edit multiple"

1. Launch app
2. Create a new account
3. Create 3 distance map expenses with 1:1 user
4. Go to reports
5. Select 2 expenses → Edit multiple
6. Enter description as <Shahrukh,khan>
7. Tap Save
8. Open the expense

Expected Result:
Specific description entered using edit multiple must be saved.

---

Test 16: IOU expenses can be changed to 0 amount by bulk editing

1. Go to 1:1 DM with any user
2. Submit two expenses
3. Open the report
4. Select both expenses
5. Click dropdown button → Edit multiple
6. Click Amount
7. Enter zero → Save → Save

Expected Result:
Error will show up on amount page because IOU expenses cannot be changed to 0 amount.

---

Test 17: User can bulk edit splits to amount larger than original amount

1. Go to workspace chat
2. Create an expense
3. Open the expense report
4. Click More → Split → Save
5. Select both expenses via checkbox
6. Click dropdown button

Expected Result:
Edit multiple option should not be available.

---

Test 18: Merchant can be removed by bulk editing with (none)

1. Go to workspace chat
2. Create at least two expenses
3. Open the report
4. Select all expenses
5. Click More → Edit expenses
6. Click Merchant
7. Enter (none) and save it → Save
8. Open any edited expense

Expected Result:
Error will show up when entering invalid merchant such as (none).

---

Test 19: IOU expenses can be changed to non-reimbursable by bulk editing

1. Go to 1:1 DM with any user
2. Create at least two expenses
3. Open the report
4. Select all expenses
5. Click More → Edit expenses

Expected Result:
IOU expenses should have no reimbursable option.

---

Test 20: Edit multiple option is missing for unreported expenses

1. Go to Self DM
2. Create two expenses
3. Go to Reports → Expenses
4. Select both expenses via checkbox
5. Click dropdown button

Expected Result:
Edit multiple option should be present for unreported expenses (it is possible to bulk edit unreported expenses on OD).

---

Test 21: Date field is disabled when bulk editing per diem expenses

Precondition: Workspace has per diem rates.

1. Go to workspace chat
2. Create two per diem expenses
3. Open the report
4. Select both per diem expenses
5. Click dropdown button → Edit multiple
6. Click Date

Expected Result:
Date field should be enabled when bulk editing per diem expenses (we can bulk edit date for per diem expenses on OD).

---

Test 22: Markdown is not applied in the description when bulk editing expenses

1. Go to workspace chat
2. Create at least two expenses
3. Open the report
4. Select all expenses
5. Click More → Edit expenses
6. Click Description
7. Enter text with markdown and save it → Save
8. Open any edited expense

Expected Result:
Markdown will be applied in the description.

---

Test 23: Expenses deselect after "Edit Multiple" is executed

1. Select 2+ expenses → "Edit multiple"
2. Make a change → Press Save

Verify:

• After Save completes, all previously selected expenses are deselected

---

Test 24: Big gap between "Save" and keyboard on "Description" when multiple editing offline — Android

Platform: Android only

Precondition: Account has at least one workspace.

1. Open the Expensify app
2. Open any workspace chat
3. Create two manual expenses
4. Open the report of the just created expenses
5. Turn off internet connection
6. Open one of the expenses and navigate to "Description"
7. Note that gap between "Save" button and keyboard is normal
8. Return to report
9. Select both expenses
10. Tap on dropdown menu and select "Edit Multiple"
11. Navigate to "Description"
12. Note that gap between "Save" button and keyboard is now bigger
13. Turn on internet connection again
14. Note that gap is now normal again

Expected Result:
Gap between "Save" button and keyboard should be the same while editing "Description" on a single expense and when multiple editing expenses.

---

Test 25: Last category is hidden behind device navigation bar — Android

Platform: Android only

Precondition: Set device navigation to navigation bar instead of swipe gestures.

1. Launch Expensify app
2. Go to workspace chat
3. Create two expenses
4. Open the expense report
5. Select both expenses by long tapping on the expense → tap Select
6. Tap dropdown button → Edit expenses
7. Tap Category
8. Scroll down to the bottom of the list

Expected Result:
The last category will appear above device navigation bar.

---

Test 26: Reimbursable and Billable fields are present when bulk editing self DM expenses

Precondition:

• Rules are enabled.
• Billable default is set to Billable in Rules settings.

1. Go to Self DM
2. Create two expenses
3. Go to Reports → Expenses
4. Select both expenses
5. Tap dropdown → Edit multiple

Verify:

• Reimbursable and Billable fields are visible on the bulk edit page

---

Test 27: Second level tag is not shown when the first level tag is not selected

Precondition: Workspace has multi-level (dependent) tags.

1. Create 2+ expenses on that workspace
2. Select them → "Edit multiple"
3. Tap Tag — do not select any first-level tag

Verify:

• Second-level tag field is not shown until a first-level tag is selected

---

Test 28: Tax rate change system message dismisses after dismissing the error

Precondition:

• Create two workspaces.
• Enable Taxes on both workspaces.
• Create 10% tax rate on the default workspace.

1. Create an expense in both workspaces.
2. Select them → "Edit multiple"
3. Tap Tax Rate
4. Select 10% rate
5. Click save
6. Open the expense from the second workspace.
7. Dismiss the error on the tax rate change

Verify:

• The 10% rate is hidden

---

Test 29: Reimbursable field is absent when bulk editing invoice expenses

1. Go to a workspace with invoicing enabled
2. Create 2+ invoice expenses
3. Select them → "Edit multiple"

Verify:

• Reimbursable field is not visible on the bulk edit page

---

Test 30: Error shows when entering 0.00 amount when bulk editing invoice expenses

1. Go to a workspace with invoicing enabled
2. Create 2+ invoice expenses
3. Select them → "Edit multiple"
4. Tap Amount → enter 0.00 → Save

Verify:

• An error message is shown on the amount page

---

Test 31: Tax amount updates after bulk editing tax rate offline

Precondition: Workspace has tax tracking enabled.

1. Create 2+ expenses with 0% tax rate.
2. Go offline
3. Open the report.
4. Bulk select the expense → Edit multiple
5. Tap Tax Rate → select 5% rate → Save
6. Open any expense.

Verify:

• Tax amount on each expense is updated to match the newly selected tax rate

---

Test 32: Negative sign can be inserted when bulk editing self DM expenses

1. Go to Self DM
2. Create two expenses
3. Go to Reports → Expenses
4. Select both expenses
5. Tap dropdown → Edit multiple
6. Tap Amount

Verify:

• The negative sign (−) can be entered in the amount field

---

Test 33: Edited tax rate does not appear as a separate rate after bulk edit

Precondition:

• Workspace has tax tracking enabled.
• Have two tax rates - 5% and 10% rate.
• Set Workspace default currency to 5% rate.
• Set Foreign default currency to 10% rate.

1. Create an expense with workspace default currency.
2. Create an expense with foreign currency.
3. Open the report.
4. Select them → "Edit multiple"
5. Tap Tax Rate → select a rate → Select 5% or 10% rate. → Save
6. Click Tax.

Verify:

• The selected rate highlighted with checkmark.

---

Test 34: No false workspace violation after cross-policy bulk edit of category

1. Create expenses on at least two different workspaces
2. Go to Search → select expenses from both workspaces
3. Tap "Edit multiple"
4. Tap Category → select a category → Save

Verify:

• Cross policy bulk edit category must not show rate not valid for the workspace violation briefly in one of the expense.

---

Test 35: Tax field is hidden in bulk edit when any selected workspace has taxes disabled

Precondition: Set up Workspace A with tax tracking enabled and Workspace B with taxes disabled

1. Create expenses on both workspaces
2. Go to "Reports" > "Expenses" → select expenses from both workspaces
3. Tap "Edit multiple"

Verify:

• Tax Rate field is not shown on the bulk edit page

---

Test 36: No "Missing Category" error after bulk editing unreported expenses

1. Go to Self DM
2. Create two expenses (unreported)
3. Go to Reports → Expenses
4. Select both expenses → "Edit multiple"
5. Update any field (e.g. merchant) → Save

Verify:

• No "Missing Category" error or violation appears on the edited expenses

---

Test 37: Tag field label and tag page header show the same custom name

Precondition: Workspace has a tag list with a custom name (e.g., "Department").

1. Create 2+ expenses on that workspace
2. Select them → "Edit multiple"

Verify:

• The tag field label on the bulk edit page and the header on the tag picker page both show the same custom name (e.g., "Department")

---

Test 38: Expense details page does not show skeleton loader after bulk editing twice offline

1. Go offline
2. Create 2+ expenses
3. Select them → "Edit multiple" → update a field → Save
4. Select them again → "Edit multiple" → update another field → Save
5. Open one of the edited expenses

Verify:

• Expense details page loads normally without a skeleton loader

---

Test 39: Set category system message is not shown for IOU when there is no category row

1. Go to 1:1 DM with any user
2. Create 2+ expenses
3. Select them → "Edit multiple"
4. Update any field that does not include category → Save
5. Open the transaction thread of one edited expense

Verify:

• No "Set category" system message is shown

---

Test 40: Default custom tax name shown correctly in bulk edit

Precondition: Workspace has a default tax rate with a custom name (not "Tax rate").

1. Create 2+ expenses on that workspace
2. Select them → "Edit multiple"
3. Tap Tax Rate

Verify:

• The default tax entry shows the custom name, not "Tax rate"

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

Same as tests

• Verify that no errors appear in the JS console

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

Android: Native

android-native-converted.webm

Android: mWeb Chrome

android-web-converted.webm

iOS: Native

ios-native-converted.mov

iOS: mWeb Safari

ios-web-converted.mov

MacOS: Chrome / Safari

web-converted.mov

[melvin-bot]

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

1. Look at the code and make sure there are no malicious changes.
2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

[pasyukevich]

Bulk Edit Issues Tracking

• Expense - Reimbursable and Billable fields are missing when bulk editing self DM expenses #84644 — Expense - Reimbursable and Billable fields are missing when bulk editing self DM expenses
• Expenses - Second level tag is shown when the first level tag is not selected #84648 — Expenses - Second level tag is shown when the first level tag is not selected
• Bulk edit - Tax rate change system message does not dismiss after dismissing the error #84649 — Bulk edit - Tax rate change system message does not dismiss after dismissing the error
• Expense - Reimbursable field is present when bulk editing invoice expenses #84663 — Expense - Reimbursable field is present when bulk editing invoice expenses
• Expense - No error shows up when 0.00 amount when bulk editing invoice expenses #84665 — Expense - No error shows up when 0.00 amount when bulk editing invoice expenses
• Expense - Tax amount field does not update after bulk editing tax rate offline #84666 — Expense - Tax amount field does not update after bulk editing tax rate offline
• Expense - Negative sign cannot be inserted when bulk editing self DM expenses #84668 — Expense - Negative sign cannot be inserted when bulk editing self DM expenses
• Expense - Selected tax rate appears as a separate rate when bulk editing expenses #84671 — Expense - Selected tax rate appears as a separate rate when bulk editing expenses
• Expense-Cross policy bulk edit category shows rate not valid for workspace violation briefly #84675 — Expense - Cross policy bulk edit category shows rate not valid for workspace violation briefly
• Expense - Tax field present in cross policy bulk edit, despite one WS having taxes disabled #84678 — Expense - Tax field present in cross policy bulk edit, despite one WS having taxes disabled
• Expense - "Missing Category" error message appears after bulk editing unreported expenses. #84683 — Expense - "Missing Category" error message appears after bulk editing unreported expenses
• Expenses - Tag field and tag page header show different name when tag has custom name #84684 — Expenses - Tag field and tag page header show different name when tag has custom name
• Expense - Expense details page shows skeleton loader after bulk editing expenses twice offline #84689 — Expense - Expense details page shows skeleton loader after bulk editing expenses twice offline
• Expense - Set the category system message is shown for IOU when no category row. #84693 — Expense - Set the category system message is shown for IOU when no category row
• Expense - Default Custom Tax Name Displays Incorrectly as “Tax rate” in Multiple Expense Edit #84735 — Expense - Default Custom Tax Name Displays Incorrectly as "Tax rate" in Multiple Expense Edit

[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/CONST/index.ts	95.20% <ø> (ø)
src/ONYXKEYS.ts	100.00% <ø> (ø)
src/SCREENS.ts	100.00% <ø> (ø)
src/hooks/useSelectedTransactionsActions.ts	84.09% <100.00%> (+0.56%)	⬆️
src/libs/API/types.ts	100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts	76.92% <ø> (ø)
src/libs/ReportUtils.ts	79.35% <100.00%> (+0.14%)	⬆️
src/ROUTES.ts	15.98% <0.00%> (-0.02%)	⬇️
...c/components/ReportActionItem/MoneyRequestView.tsx	66.50% <0.00%> (+2.18%)	⬆️
src/libs/SearchUIUtils.ts	68.34% <92.85%> (+0.16%)	⬆️
... and 21 more
... and 14 files with indirect coverage changes

[pasyukevich]

Updates:

Wasn't able to reproduce:
#84693 — Expense - Set the category system message is shown for IOU when no category row

Current focus:
#84689 — Expense - Expense details page shows skeleton loader after bulk editing expenses twice offline - The issue has been reproduced, and I’m currently investigating the root cause. The problem is more complex than initially expected.

In progress
#84649 — Bulk edit - Tax rate change system message does not dismiss after dismissing the error
#84735 — Expense - Default Custom Tax Name Displays Incorrectly as "Tax rate" in Multiple Expense Edit

Next steps:

• Fix remaining issues
• Fix tests
• Update test steps and record videos
• Review
• QA round before merge
• Fix if smth new detected

[pasyukevich]

Updates:

• All issues fixed
• Failing tests fixed

Next steps :

• Update test steps and record videos
• Review
• QA round before merge
• Fix if smth new detected

[MelvinBot]

I ran out of time before I could finish helping you. This usually means the task was too complex or I got stuck exploring. Please try again with a more specific request or post in the #melvinbot-ai.

Run details: https://github.com/Expensify/Expensify/actions/runs/23816895655

[jponikarchuk]

This PR failing because of the issue #86841
This issue is reproducible in: Web

[jponikarchuk]

Deploy Blocker #86841 was identified to be related to this PR.

[jponikarchuk]

Deploy Blocker #86842 was identified to be related to this PR.

[mitarachim]

Deploy Blocker #86855 was identified to be related to this PR.

[OSBotify]

🚀 Deployed to production by https://github.com/jasperhuangg in version: 9.3.51-10 🚀

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

[LukasMod]

@pasyukevich Could you replace Test 8 with more clear steps? Proposition based on this PR below. I skip offline test as its already in Test 9. cc @Krishna2323

Test 8: Optimistic updates — failure and slow network

Test 8a: 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 8b: 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

[rojiphil]

A loading spinner was added in #90707 to prevent the user from repeatedly tapping the button.