[$250] Split Expense - “Not here page” is displayed in the expense after returning online.

[jponikarchuk]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.3.31-2
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-7606/folder/13177049/41237814/1228589168
Email or phone of affected tester (no customers): joelarmandotester+725@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: MacOS 15.7.3 / Chrome
App Component: Money Requests

Action Performed:

1. Goto staging.new.expensify.com
2. Sign in to an account
3. Go to a 1:1 DM.
4. Go offline.
5. Create a split expense.
6. Open the expense created.
7. Go online.

Expected Result:

The expense details should be displayed correctly when you return online.

Actual Result:

“Not here page” is displayed in the expense after returning online.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

1.mov

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @abzokhattab

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022043665075073569923
• Upwork Job ID: 2043665075073569923
• Last Price Increase: 2026-04-13

[nabi-ebrahimi]

Proposal

Please re-state the problem that we are trying to solve in this issue.

When a split expense is created, opening the child expense and then reconnecting shows the “Not here” page instead of keeping the expense details visible.

What is the root cause of that problem?

The active split-expense flow enters through splitBill() in Split.ts, and that function delegates the optimistic split construction to createSplitsAndOnyxData()

Inside that builder, the oneOnOneIOUReport is created first in Step 2. Then, in Step 4, the flow resolves the parent REPORTPREVIEW by reusing an existing preview if one already exists, or creating a new one otherwise:

The problem is that the split flow does not link the child IOU report back to that resolved preview action before writing the optimistic report to Onyx. buildOnyxDataForMoneyRequest() stores the child report from optimisticParams.iou.report

So the optimistic state becomes:

• the child IOU report exists
• the parent REPORTPREVIEW action exists
• but the child IOU report does not contain parentReportActionID

That missing linkage matters because the expense page resolves the parent action only by reading report.parentReportActionID:

App/src/hooks/useParentReportAction.ts

Lines 9 to 29 in 43a57cf

	function useParentReportAction(report: OnyxEntry<Report>) {
	const getParentReportAction = useCallback(
	(parentReportActions: OnyxEntry<ReportActions>) => getParentReportActionSelector(parentReportActions, report?.parentReportActionID),
	[report?.parentReportActionID],
	);
	const parentReportID = getNonEmptyStringOnyxID(report?.parentReportID);
	const [parentReportAction] = useOnyx(
	`${ONYXKEYS.COLLECTION.REPORT_ACTIONS}${parentReportID}`,
	{
	// Only set canEvict when we have a valid parentReportID — reportActions_<id> is an evictable key,
	// but reportActions_undefined is not and will throw if canEvict is specified.
	canEvict: parentReportID ? false : undefined,
	selector: getParentReportAction,
	},
	[getParentReportAction],
	);
	return parentReportAction;

Then SearchMoneyRequestReportPage passes that into getParentReportActionDeletionStatus():

App/src/pages/Search/SearchMoneyRequestReportPage.tsx

Lines 169 to 175 in 43a57cf

	const {wasParentActionDeleted} = getParentReportActionDeletionStatus({
	parentReportID: report?.parentReportID,
	parentReportActionID: report?.parentReportActionID,
	parentReportAction,
	parentReportMetadata,
	isOffline,
	});

That helper treats a loaded-but-unresolved parent action as missing and once wasParentActionDeleted becomes true,
SearchMoneyRequestReportPage flips shouldShowAccessErrorPage to true and renders FullPageNotFoundView:

So the root cause is:

• the split flow resolves the correct parent preview action
• but it does not copy that action’s reportActionID onto the optimistic child IOU report
• the expense page later depends on that field to resolve the parent action
• the missing linkage drives the page into the wasParentActionDeleted -> shouldShowAccessErrorPage -> FullPageNotFoundView path

For comparison, This flow already links the child report to the preview action:

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

Lines 3626 to 3636 in 43a57cf

	let reportPreviewAction = shouldCreateNewMoneyRequestReport ? null : getReportPreviewAction(chatReport.reportID, iouReport.reportID);
	if (reportPreviewAction) {
	reportPreviewAction = updateReportPreview(iouReport, reportPreviewAction, false, comment, optimisticTransaction);
	} else {
	reportPreviewAction = buildOptimisticReportPreview(chatReport, iouReport, comment, optimisticTransaction, undefined, optimisticReportPreviewActionID);
	chatReport.lastVisibleActionCreated = reportPreviewAction.created;
	// Generated ReportPreview action is a parent report action of the iou report.
	// We are setting the iou report's parentReportActionID to display subtitle correctly in IOU page when offline.
	iouReport.parentReportActionID = reportPreviewAction.reportActionID;

What changes do you think we should make in order to solve the problem?

Link the split child IOU report to the resolved parent REPORTPREVIEW action in createSplitsAndOnyxData(), immediately before buildOnyxDataForMoneyRequest() writes the report to Onyx.

diff --git a/src/libs/actions/IOU/index.ts b/src/libs/actions/IOU/index.ts
index 7860da05a9b..719d176a7c8 100644
--- a/src/libs/actions/IOU/index.ts
+++ b/src/libs/actions/IOU/index.ts
@@ -8219,6 +8219,10 @@ function createSplitsAndOnyxData({
             oneOnOneReportPreviewAction = buildOptimisticReportPreview(oneOnOneChatReport, oneOnOneIOUReport);
         }
 
+        // The preview action is the parent action for the split child IOU report.
+        // We link it here before writing the report to Onyx so the expense page can resolve the parent action.
+        oneOnOneIOUReport.parentReportActionID = oneOnOneReportPreviewAction.reportActionID;
+
         const optimisticPolicyRecentlyUsedCategories = isPolicyExpenseChat ? mergePolicyRecentlyUsedCategories(category, policyRecentlyUsedCategories) : [];
         const optimisticRecentlyUsedCurrencies = mergePolicyRecentlyUsedCurrencies(currency, policyRecentlyUsedCurrencies);

What alternative solutions did you explore? (Optional)

Reverse the order by pre-generating a preview reportActionID, assigning it while oneOnOneIOUReport is first created, and then passing that ID into buildOptimisticReportPreview().

That would also work, because buildOptimisticReportPreview() accepts an optional reportActionID:

App/src/libs/ReportUtils.ts

Lines 7483 to 7490 in 43a57cf

	function buildOptimisticReportPreview(
	chatReport: OnyxInputOrEntry<Report>,
	iouReport: Report,
	comment = '',
	transaction: OnyxInputOrEntry<Transaction> = null,
	childReportID?: string,
	reportActionID?: string,
	): ReportAction<typeof CONST.REPORT.ACTIONS.TYPE.REPORT_PREVIEW> {

DEMO

Screencast.from.2026-03-09.16-46-34.webm

[MelvinBot]

Proposal

What is the root cause of that problem?

In createSplitsAndOnyxData(), the child IOU report's parentReportActionID is never linked to the resolved REPORT_PREVIEW action. After the preview action is resolved at IOU/index.ts:4027-4032, the IOU report is written to Onyx (via buildOnyxDataForMoneyRequest) without this field.

When the expense page opens, useParentReportAction reads report.parentReportActionID — which is undefined — causing getParentReportActionDeletionStatus() to treat the parent action as deleted, which flips shouldShowAccessErrorPage to true and renders the "Not here" page.

The non-split flow correctly sets this field at IOU/index.ts:2578-2580 with the comment: "We are setting the iou report's parentReportActionID to display subtitle correctly in IOU page when offline."

What changes do you think we should make in order to solve the problem?

Set oneOnOneIOUReport.parentReportActionID = oneOnOneReportPreviewAction.reportActionID in createSplitsAndOnyxData(), immediately after the report preview action is resolved and before buildOnyxDataForMoneyRequest() writes the report to Onyx. This matches the pattern already used by the non-split flow.

Investigation details

Evidence chain:

1. buildOptimisticIOUReport is called at line 3948 without a parentReportActionID parameter
2. oneOnOneReportPreviewAction is resolved at lines 4027-4032 but its ID is never assigned back to the IOU report
3. useParentReportAction (hook) reads the missing field → returns undefined
4. getParentReportActionDeletionStatus in TransactionNavigationUtils.ts computes wasParentActionDeleted = true
5. SearchMoneyRequestReportPage at line 333 shows FullPageNotFoundView

Note: The current codebase has a shouldRequireParentReportActionID guard that may mitigate the visible symptom in newer builds, but the underlying data inconsistency (missing field) still exists and the fix is correct regardless.

Existing proposal by nabi-ebrahimi identified the same root cause and proposed the same fix with a working demo video.

Possibly related open issues:

• [$250] Broken report page and report review after removing split #87094 — Broken report page after removing split
• [$250] Expense report- Restored Expense detail preview is empty after go back online #87065 — Restored expense detail preview empty after going back online

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.