fix: Offline expense shows Outstanding from report but Paid from chat by nkdengineer · Pull Request #79536 · Expensify/App

nkdengineer · 2026-01-14T08:45:10Z

Explanation of Change

fix: Offline expense shows Outstanding from report but Paid from chat

Fixed Issues

$ #79027
PROPOSAL: #79027 (comment)

Tests

Tap to the "Reports" tab
Go offline
Click on "Create expense"
Tap on "Manual"
Add an amount and tap on "Next"
In Choose recipient page, select "Manager McTest"
Create and open the expense
Verify that the Marked as paid system message appears, header shows paid status

Verify that no errors appear in the JS console

Offline tests

Same

QA Steps

Same as test

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Screen.Recording.2026-01-14.at.17.56.45.mov

Android: mWeb Chrome

Screen.Recording.2026-01-14.at.18.00.27.mov

iOS: Native

Screen.Recording.2026-01-14.at.17.58.57.mov

iOS: mWeb Safari

Screen.Recording.2026-01-14.at.17.57.58.mov

MacOS: Chrome / Safari

Screen.Recording.2026-01-14.at.17.54.23.mov

codecov · 2026-01-14T08:55:40Z

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/actions/IOU/index.ts	`67.98% <20.00%> (-0.04%)`	⬇️
... and 64 files with indirect coverage changes

melvin-bot · 2026-01-14T11:02:18Z

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

eVoloshchak · 2026-01-15T15:54:24Z

src/libs/actions/IOU/index.ts

+                ? {lastActionType: CONST.REPORT.ACTIONS.TYPE.MARKED_REIMBURSED, stateNum: CONST.REPORT.STATE_NUM.APPROVED, statusNum: CONST.REPORT.STATUS_NUM.REIMBURSED}
+                : undefined),
+            hasOutstandingChildRequest: false,
+            lastActorAccountID: deprecatedCurrentUserPersonalDetails?.accountID,


Is there a reason we're using a deprecated variable?

@eVoloshchak I just copied the value here.

App/src/libs/actions/IOU/index.ts

Lines 1905 to 1932 in e94f05d

value: {

...iou.report,

...(!isScanRequest || isTestReceipt

? {lastActionType: CONST.REPORT.ACTIONS.TYPE.MARKED_REIMBURSED, stateNum: CONST.REPORT.STATE_NUM.APPROVED, statusNum: CONST.REPORT.STATUS_NUM.REIMBURSED}

: undefined),

hasOutstandingChildRequest: false,

lastActorAccountID: deprecatedCurrentUserPersonalDetails?.accountID,

},

},

{

onyxMethod: Onyx.METHOD.MERGE,

key: `${ONYXKEYS.COLLECTION.REPORT_ACTIONS}${iou.report.reportID}`,

value: {

[iou.action.reportActionID]: {

...(optimisticIOUReportAction as OnyxTypes.ReportAction),

},

},

},

{

onyxMethod: Onyx.METHOD.MERGE,

key: `${ONYXKEYS.COLLECTION.TRANSACTION}${transaction.transactionID}`,

value: {

...transaction,

},

},

);

}

Yes, but this was the last place that was using deprecatedCurrentUserPersonalDetails, it would be perfect if we could get rid of it instead of increasing the usage (if possible, this isn't performance critical so not worth a refactor or anything of that nature). Could we pass the account id from the useCurrentUserPersonalDetails hook easily?

@eVoloshchak Since we already used this variable in this function, I think it's not a problem if we use it again in this function. When we refactor this function, it doesn't increase the complexity. It's a problem if we use this variable in a function that didn't use this before

eVoloshchak · 2026-01-22T13:24:19Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified there are no new alerts related to the canBeMissing param for useOnyx
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

Screen.Recording.2026-01-22.at.14.34.17.mov

Android: mWeb Chrome

Screen.Recording.2026-01-22.at.14.35.31.mov

iOS: HybridApp

Screen.Recording.2026-01-22.at.14.29.04.mov

iOS: mWeb Safari

Screen.Recording.2026-01-22.at.14.30.55.mov

MacOS: Chrome / Safari

Screen.Recording.2026-01-22.at.14.23.18.mov

eVoloshchak

LGTM!

OSBotify · 2026-01-22T17:16:52Z

✋ 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-01-22T22:53:38Z

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

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

jponikarchuk · 2026-01-23T06:24:04Z

This PR failing because of an issue in offline mode
This issue is reproducible in: All platforms

OSBotify · 2026-01-23T22:04:59Z

🚀 Deployed to production by https://github.com/Beamanator in version: 9.3.7-3 🚀

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

fix: Offline expense shows Outstanding from report but Paid from chat

8349174

melvin-bot bot assigned nkdengineer Jan 14, 2026

nkdengineer marked this pull request as ready for review January 14, 2026 11:02

nkdengineer requested review from a team as code owners January 14, 2026 11:02

melvin-bot bot requested review from JmillsExpensify and eVoloshchak January 14, 2026 11:02

melvin-bot bot removed request for a team and JmillsExpensify January 14, 2026 11:02

eVoloshchak reviewed Jan 15, 2026

View reviewed changes

nkdengineer added 2 commits January 16, 2026 14:14

Merge branch 'main' into fix/79027

cabed7c

Merge branch 'main' into fix/79027

ad212cd

eVoloshchak approved these changes Jan 22, 2026

View reviewed changes

melvin-bot bot requested a review from mjasikowski January 22, 2026 13:40

mjasikowski approved these changes Jan 22, 2026

View reviewed changes

mjasikowski merged commit b023351 into Expensify:main Jan 22, 2026
30 checks passed

OSBotify mentioned this pull request Jan 22, 2026

Deploy Checklist: New Expensify 2026-01-22 #80277

Closed

63 tasks

OSBotify mentioned this pull request Jan 23, 2026

Expense - Expense disappear from workspace after editing any fields in expense details #80301

Closed

7 tasks

jponikarchuk mentioned this pull request Jan 23, 2026

Reports - “Marked as paid” system message does not appear while offline #80308

Closed

7 tasks

melvin-bot bot mentioned this pull request Jan 23, 2026

[Due for payment 2026-01-30] [$250] Expense - Offline expense shows Outstanding from report but Paid from chat #79027

Closed

7 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix: Offline expense shows Outstanding from report but Paid from chat#79536

fix: Offline expense shows Outstanding from report but Paid from chat#79536
mjasikowski merged 3 commits intoExpensify:mainfrom
nkdengineer:fix/79027

nkdengineer commented Jan 14, 2026 •

edited

Loading

Uh oh!

codecov bot commented Jan 14, 2026 •

edited by github-actions bot

Loading

Uh oh!

melvin-bot bot commented Jan 14, 2026

Uh oh!

eVoloshchak Jan 15, 2026

Uh oh!

nkdengineer Jan 16, 2026

Uh oh!

eVoloshchak Jan 19, 2026

Uh oh!

nkdengineer Jan 21, 2026

Uh oh!

eVoloshchak commented Jan 22, 2026 •

edited

Loading

Uh oh!

eVoloshchak left a comment

Uh oh!

Uh oh!

OSBotify commented Jan 22, 2026

Uh oh!

OSBotify commented Jan 22, 2026

Uh oh!

jponikarchuk commented Jan 23, 2026

Uh oh!

OSBotify commented Jan 23, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

	value: {
	...iou.report,
	...(!isScanRequest \|\| isTestReceipt
	? {lastActionType: CONST.REPORT.ACTIONS.TYPE.MARKED_REIMBURSED, stateNum: CONST.REPORT.STATE_NUM.APPROVED, statusNum: CONST.REPORT.STATUS_NUM.REIMBURSED}
	: undefined),
	hasOutstandingChildRequest: false,
	lastActorAccountID: deprecatedCurrentUserPersonalDetails?.accountID,
	},
	},
	{
	onyxMethod: Onyx.METHOD.MERGE,
	key: `${ONYXKEYS.COLLECTION.REPORT_ACTIONS}${iou.report.reportID}`,
	value: {
	[iou.action.reportActionID]: {
	...(optimisticIOUReportAction as OnyxTypes.ReportAction),
	},
	},
	},
	{
	onyxMethod: Onyx.METHOD.MERGE,
	key: `${ONYXKEYS.COLLECTION.TRANSACTION}${transaction.transactionID}`,
	value: {
	...transaction,
	},
	},
	);
	}

Conversation

nkdengineer commented Jan 14, 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 Jan 14, 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 Jan 14, 2026

Uh oh!

eVoloshchak Jan 15, 2026

Choose a reason for hiding this comment

Uh oh!

nkdengineer Jan 16, 2026

Choose a reason for hiding this comment

Uh oh!

eVoloshchak Jan 19, 2026

Choose a reason for hiding this comment

Uh oh!

nkdengineer Jan 21, 2026

Choose a reason for hiding this comment

Uh oh!

eVoloshchak commented Jan 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

eVoloshchak left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

OSBotify commented Jan 22, 2026

Uh oh!

OSBotify commented Jan 22, 2026

Uh oh!

jponikarchuk commented Jan 23, 2026

Uh oh!

OSBotify commented Jan 23, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

nkdengineer commented Jan 14, 2026 •

edited

Loading

codecov bot commented Jan 14, 2026 •

edited by github-actions bot

Loading

eVoloshchak commented Jan 22, 2026 •

edited

Loading