Skip to content

fix: pass iouReport instead of chatReport for smartscan field check#86727

Merged
NikkiWines merged 7 commits intoExpensify:mainfrom
callstack-internal:fix/smartscan-iou-report-lookup
Apr 7, 2026
Merged

fix: pass iouReport instead of chatReport for smartscan field check#86727
NikkiWines merged 7 commits intoExpensify:mainfrom
callstack-internal:fix/smartscan-iou-report-lookup

Conversation

@sosek108
Copy link
Copy Markdown
Contributor

@sosek108 sosek108 commented Mar 31, 2026

Explanation of Change

getReportActionWithMissingSmartscanFields (and the related shouldShowRBRForMissingSmartscanFields / hasSmartscanError / getReportActionWithSmartscanError chain) was receiving the chat report and forwarding it to hasMissingSmartscanFields. That utility evaluates areRequiredFieldsEmpty with isFromExpenseReport derived from the report it receives — when given the chat report instead of the expense (IOU) report, isFromExpenseReport is always false, which makes a $0 amount incorrectly pass the smartscan error check and show a "Fix" badge in the LHN even when there is no real error.

The fix threads reports: OnyxCollection<Report> through the call chain (generateReportAttributesgetAllReportErrorsgetAllReportActionsErrorsAndReportActionThatRequiresAttentionhasSmartscanError / getReportActionWithSmartscanError) so that getReportActionWithSmartscanError can look up the actual IOU/expense report by IOUReportID and pass it to shouldShowRBRForMissingSmartscanFields / getReportActionWithMissingSmartscanFields. When the IOU report is not found in the collection it falls back to the original report, preserving existing behaviour for non-preview actions.

Fixed Issues

$ #86109
PROPOSAL:

Tests

  1. Open the Exfy
  2. Open any workspace chat.
  3. Create a manual expense with "0" as amount.
  4. Check if a "Fix" label appears on chat preview on LHN.
  5. Open the just created expense. Confirm that information on report and LHN is the same

Offline tests

N/A

QA Steps

  1. Open the Exfy
  2. Open any workspace chat.
  3. Create a manual expense with "0" as amount.
  4. Check if a "Fix" label appears on chat preview on LHN.
  5. Open the just created expense. Confirm that information on report and LHN is the same

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: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

@sosek108 sosek108 marked this pull request as ready for review April 1, 2026 08:16
@sosek108 sosek108 requested review from a team as code owners April 1, 2026 08:16
@melvin-bot melvin-bot bot requested review from heyjennahay and thesahindia and removed request for a team April 1, 2026 08:16
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Apr 1, 2026

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

@codecov
Copy link
Copy Markdown

codecov bot commented Apr 1, 2026

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/ReportUtils.ts 80.40% <100.00%> (-0.04%) ⬇️
src/libs/SidebarUtils.ts 80.61% <100.00%> (ø)
...bs/actions/OnyxDerived/configs/reportAttributes.ts 96.79% <ø> (ø)
... and 8 files with indirect coverage changes

@NikkiWines NikkiWines requested a review from aimane-chnaif April 1, 2026 13:13
@NikkiWines
Copy link
Copy Markdown
Contributor

@thesahindia, @aimane-chnaif will review this since it's related to a PR they authored - see here

@NikkiWines NikkiWines removed the request for review from thesahindia April 1, 2026 13:14
@MelvinBot
Copy link
Copy Markdown
Contributor

🤖 MelvinBot Code Review

Overall: This is a well-targeted fix. The root cause is correctly identified and the fix is sound. All CI checks pass.

What the PR does right

The core bug: getReportActionWithSmartscanError was passing the chat report to shouldShowRBRForMissingSmartscanFieldshasMissingSmartscanFieldsareRequiredFieldsEmpty. Since areRequiredFieldsEmpty checks report?.type === 'expense' to set isFromExpenseReport, passing a chat report (type: 'chat') always yielded isFromExpenseReport === false, which activates the getAmount(transaction) === 0 check — falsely flagging $0 manual expenses as smartscan errors.

The fix correctly:

  • Looks up the actual IOU report via reports?.[ONYXKEYS.COLLECTION.REPORT + IOUReportID]
  • Falls back to the original report when the IOU report isn't in the collection
  • Threads the reports collection through the call chain with optional parameters, avoiding breaking changes

Non-blocking observations

  1. Line 10848 — The split/track action path still passes report (the chat report) to hasMissingSmartscanFieldsTransactionUtils:

    const isTransactionThreadError = isSplitOrTrackAction && hasMissingSmartscanFieldsTransactionUtils(transaction as Transaction, report);

    Since getIOUReportIDFromReportActionPreview returns undefined for non-preview actions, iouReport is always undefined here, so iouReport ?? report would still give report. This is a pre-existing issue (not a regression from this PR), but for workspace chat split bills where the IOU report type is 'expense', the wrong validation branch (amount vs merchant) could be triggered. Worth a follow-up if split bill smartscan errors are also affected.

  2. MoneyReportHeader.tsx:661 — Calls getAllReportActionsErrorsAndReportActionThatRequiresAttention(moneyRequestReport, reportActionsObject) without reports. This is fine because moneyRequestReport is already the IOU/expense report, so the fallback iouReport ?? report correctly uses moneyRequestReport.

  3. DebugUtils.ts — Calls getReasonAndReportActionThatHasRedBrickRoad without reports. Acceptable for debug tooling — the fallback preserves existing behavior.

Cat fact: A group of cats is called a "clowder," while a group of kittens is called a "kindle."

@aimane-chnaif
Copy link
Copy Markdown
Contributor

aimane-chnaif commented Apr 1, 2026

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: mWeb Chrome
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.2026-04-01.at.4.06.15.pm.mov

@aimane-chnaif
Copy link
Copy Markdown
Contributor

production: (the bug already exists in production. showing RBR)

produciton

staging: (showing "Fix")

staging

this branch:

this branch

Copy link
Copy Markdown
Contributor

@aimane-chnaif aimane-chnaif left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MelvinBot can you help with automated tests to prevent such bugs in the future?
Just provide code diff.

@melvin-bot melvin-bot bot requested a review from NikkiWines April 1, 2026 15:16
@MelvinBot
Copy link
Copy Markdown
Contributor

Here's a test diff that covers the exact regression scenario from this PR — ensuring getReportActionWithSmartscanError uses the expense report (via the reports collection) rather than the chat report for smartscan field validation.

Add the following describe block to tests/unit/ReportUtilsTest.ts:

--- a/tests/unit/ReportUtilsTest.ts
+++ b/tests/unit/ReportUtilsTest.ts
@@ -35,6 +35,8 @@
     buildOptimisticIOUReportAction,
+    getReportActionWithSmartscanError,
+    hasSmartscanError,
     buildOptimisticReportPreview,

Then add the test block (at the end of the top-level describe('ReportUtils', ...), before the closing });):

+    describe('getReportActionWithSmartscanError', () => {
+        const chatReportID = '100';
+        const expenseReportID = '200';
+        const transactionID = '300';
+        const iouReportActionID = '400';
+
+        const chatReport: Report = {
+            ...LHNTestUtils.getFakeReport(),
+            reportID: chatReportID,
+            type: CONST.REPORT.TYPE.CHAT,
+        };
+
+        const expenseReport: Report = {
+            ...LHNTestUtils.getFakeReport(),
+            reportID: expenseReportID,
+            type: CONST.REPORT.TYPE.EXPENSE,
+            parentReportID: chatReportID,
+            ownerAccountID: currentUserAccountID,
+            statusNum: CONST.REPORT.STATUS_NUM.OPEN,
+        };
+
+        // Transaction with $0 amount but valid merchant and created date.
+        // On an expense report this should NOT be a smartscan error (amount is
+        // irrelevant; only merchant matters).  On a chat report the old code path
+        // would incorrectly flag getAmount(txn) === 0 as a missing field.
+        const transaction: Transaction = {
+            ...createRandomTransaction(Number(transactionID)),
+            transactionID,
+            reportID: expenseReportID,
+            amount: 0,
+            merchant: 'Coffee Shop',
+            modifiedMerchant: '',
+            created: testDate,
+        };
+
+        // Money‑request (IOU) action that lives inside the expense report's actions
+        const iouAction = {
+            ...createRandomReportAction(Number(iouReportActionID)),
+            reportActionID: iouReportActionID,
+            actionName: CONST.REPORT.ACTIONS.TYPE.IOU as const,
+            actorAccountID: currentUserAccountID,
+            originalMessage: {
+                IOUTransactionID: transactionID,
+                IOUReportID: expenseReportID,
+                type: CONST.IOU.REPORT_ACTION_TYPE.CREATE,
+                amount: 0,
+                currency: CONST.CURRENCY.USD,
+                comment: '',
+                participantAccountIDs: [currentUserAccountID],
+            },
+        };
+
+        // REPORT_PREVIEW action that sits in the chat report and links to the expense report
+        const reportPreviewAction = buildOptimisticReportPreview(chatReport, expenseReport as Report, '', transaction);
+
+        beforeAll(async () => {
+            await Onyx.multiSet({
+                [ONYXKEYS.SESSION]: {email: currentUserEmail, accountID: currentUserAccountID},
+                [`${ONYXKEYS.COLLECTION.TRANSACTION}${transactionID}`]: transaction,
+                [`${ONYXKEYS.COLLECTION.REPORT_ACTIONS}${expenseReportID}`]: {
+                    [iouReportActionID]: iouAction,
+                },
+            });
+            return waitForBatchedUpdates();
+        });
+
+        it('should NOT flag $0 manual expense as smartscan error when expense report is resolved via reports collection', () => {
+            // With the reports collection the function can look up the actual
+            // expense report (type 'expense') via IOUReportID.  For expense
+            // reports areRequiredFieldsEmpty checks isMerchantMissing (not
+            // amount), so a $0 expense with a valid merchant is fine.
+            const reportsCollection = {
+                [`${ONYXKEYS.COLLECTION.REPORT}${expenseReportID}`]: expenseReport,
+            };
+
+            const result = getReportActionWithSmartscanError([reportPreviewAction], chatReport, reportsCollection);
+            expect(result).toBeUndefined();
+            expect(hasSmartscanError([reportPreviewAction], chatReport, reportsCollection)).toBe(false);
+        });
+
+        it('should flag smartscan error when expense report has a missing merchant', async () => {
+            // Replace the transaction with one that has an empty merchant
+            const txnMissingMerchant: Transaction = {
+                ...transaction,
+                merchant: '',
+                modifiedMerchant: '',
+            };
+            await Onyx.merge(`${ONYXKEYS.COLLECTION.TRANSACTION}${transactionID}`, txnMissingMerchant);
+            await waitForBatchedUpdates();
+
+            const reportsCollection = {
+                [`${ONYXKEYS.COLLECTION.REPORT}${expenseReportID}`]: expenseReport,
+            };
+
+            expect(hasSmartscanError([reportPreviewAction], chatReport, reportsCollection)).toBe(true);
+
+            // Restore original transaction for subsequent tests
+            await Onyx.merge(`${ONYXKEYS.COLLECTION.TRANSACTION}${transactionID}`, transaction);
+            await waitForBatchedUpdates();
+        });
+
+        it('should NOT flag settled (reimbursed) expense reports even with missing fields', async () => {
+            const settledExpenseReport: Report = {
+                ...expenseReport,
+                statusNum: CONST.REPORT.STATUS_NUM.REIMBURSED,
+            };
+
+            // Even with missing merchant, a settled report should not show error
+            const txnMissingMerchant: Transaction = {
+                ...transaction,
+                merchant: '',
+                modifiedMerchant: '',
+            };
+            await Onyx.merge(`${ONYXKEYS.COLLECTION.TRANSACTION}${transactionID}`, txnMissingMerchant);
+            await waitForBatchedUpdates();
+
+            const reportsCollection = {
+                [`${ONYXKEYS.COLLECTION.REPORT}${expenseReportID}`]: settledExpenseReport,
+            };
+
+            expect(hasSmartscanError([reportPreviewAction], chatReport, reportsCollection)).toBe(false);
+
+            // Restore
+            await Onyx.merge(`${ONYXKEYS.COLLECTION.TRANSACTION}${transactionID}`, transaction);
+            await waitForBatchedUpdates();
+        });
+    });

What these tests cover

Test Scenario Prevents
1 $0 expense with valid merchant on expense report → no error The exact regression: chat report was used instead of expense report, making areRequiredFieldsEmpty check amount instead of merchant
2 Missing merchant on expense report → error detected Ensures real smartscan errors are still caught
3 Settled expense report → no error even with missing fields Guards the !isSettled(IOUReportID) check

The first test is the critical regression guard — if someone removes the reports parameter threading or changes the IOU report lookup, this test will fail because the function would fall back to the chat report (type 'chat') and incorrectly flag getAmount(transaction) === 0.

Cat fact: Cats can rotate their ears 180 degrees, using 32 muscles in each ear — compared to just 6 muscles in a human ear.

@aimane-chnaif
Copy link
Copy Markdown
Contributor

@sosek108 please add unit test above. Otherwise looks good.

Copy link
Copy Markdown
Contributor

@NikkiWines NikkiWines left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm aside from @aimane-chnaif's comment above

@chatgpt-codex-connector
Copy link
Copy Markdown

Codex Review: Something went wrong. Try again later by commenting “@codex review”.

We were unable to download your code in a timely manner.
ℹ️ 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".

@sosek108
Copy link
Copy Markdown
Contributor Author

sosek108 commented Apr 2, 2026

@aimane-chnaif @NikkiWines tests added

Copy link
Copy Markdown
Contributor

@NikkiWines NikkiWines left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sosek108 typescript checks are failing

Otherwise lgtm

Copy link
Copy Markdown
Contributor

@NikkiWines NikkiWines left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

small thing


it('should flag smartscan error when expense report has a missing merchant', async () => {
// Replace the transaction with one that has an empty merchant
const txnMissingMerchant: Transaction = {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
const txnMissingMerchant: Transaction = {
const transactionMissingMerchant: Transaction = {

Avoid using abbreviated variable names (even in tests)

};

// Even with missing merchant, a settled report should not show error
const txnMissingMerchant: Transaction = {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
const txnMissingMerchant: Transaction = {
const transactionMissingMerchant: Transaction = {

@sosek108
Copy link
Copy Markdown
Contributor Author

sosek108 commented Apr 7, 2026

@NikkiWines fixed

Copy link
Copy Markdown
Contributor

@NikkiWines NikkiWines left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sosek108 could you merge main please? otherwise looks good

@sosek108
Copy link
Copy Markdown
Contributor Author

sosek108 commented Apr 7, 2026

Done, let's wait for checks to pass

@NikkiWines NikkiWines merged commit 7f29b17 into Expensify:main Apr 7, 2026
31 checks passed
@OSBotify
Copy link
Copy Markdown
Contributor

OSBotify commented Apr 7, 2026

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

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 7, 2026

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

@OSBotify
Copy link
Copy Markdown
Contributor

OSBotify commented Apr 8, 2026

🚀 Deployed to staging by https://github.com/NikkiWines in version: 9.3.54-0 🚀

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

Bundle Size Analysis (Sentry):

@MelvinBot
Copy link
Copy Markdown
Contributor

No help site changes are required for this PR.

This is a purely internal bug fix that corrects which report object (IOU/expense report vs. chat report) is passed to the smartscan field validation logic. The changes are confined to internal utilities (ReportUtils.ts, SidebarUtils.ts, reportAttributes.ts) and unit tests.

  • No user-facing features, workflows, or settings were added or changed
  • No UI labels, button names, or navigation paths were modified
  • No new terminology or concepts were introduced

The fix simply corrects an incorrect "Fix" badge from appearing on chat previews in the LHN — the badge itself is existing documented behavior that was just triggering incorrectly.

@jponikarchuk
Copy link
Copy Markdown

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

@jponikarchuk
Copy link
Copy Markdown

This PR failing because of the issue #87343
This issue is reproducible in: All platforms

@OSBotify
Copy link
Copy Markdown
Contributor

OSBotify commented Apr 9, 2026

🚀 Deployed to production by https://github.com/roryabraham in version: 9.3.54-7 🚀

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants