[$250] Expense-Split by date for 30 days shows skeleton and directs to workspace chat page

[mitarachim]

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: V9.3.2-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #78429
Email or phone of affected tester (no customers): dreamnitethedragon+yydyd373@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Redminote 10S Android 13
App Component: Money Requests

Action Performed:

1. Launch app
2. Go to workspace chat
3. Create a failed scan expense and enter all details manually ( use camera image)
4. Tap more split - date - Select a 30 day range
5. Tap save - save

Expected Result:

Split by date for 30 days must not show skeleton and directs to workspace chat page.

Actual Result:

Split by date for 30 days shows skeleton and directs to workspace chat page.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7049548_1768437399761.Screenrecorder-2026-01-15-05-54-09-330.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022011772098849633087
• Upwork Job ID: 2011772098849633087
• Last Price Increase: 2026-01-22

Issue Owner

Current Issue Owner: @truph01

[melvin-bot]

Triggered auto assignment to @laurenreidexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[annaweber830]

Proposal

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

When a user edits a split expense and chooses Split by date with a 30‑day range, tapping Save briefly shows a skeleton/loading state and then incorrectly navigates the user to the workspace chat. The expected behavior is that saving the date range should return the user to the Split Expense flow (showing the split list), without redirecting them to workspace chat.

What is the root cause of that problem?

The date range picker screen (SplitExpenseCreateDateRagePage) returns via Navigation.goBack(backTo), where backTo is currently set from the caller using Navigation.getActiveRoute().
In this modal flow, Navigation.getActiveRoute() can resolve to the underlying report route (e.g., workspace chat) rather than the Split Expense route. So when the user saves the date range, goBack(backTo) pops to workspace chat, effectively tearing down the split flow. That teardown also causes the brief skeleton/loading indicator during the transition.

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

• Change the navigation into the date range screen so that backTo is an explicit Split Expense route, not the current active route.
• Specifically, when opening “Split dates” from SplitExpensePage, build backTo using the Split Expense route generator (including the correct reportID, transactionID, and relevant params), then pass that to the date range route builder.
• Keep the date range screen’s “Save” behavior the same (it can continue calling Navigation.goBack(backTo)), but ensure backTo always points back into the split flow.
  

  App/src/pages/iou/SplitExpensePage.tsx

  Lines 410 to 412 in 8f123f4

  	const handleDatePress = useCallback(() => {
  	Navigation.navigate(ROUTES.SPLIT_EXPENSE_CREATE_DATE_RANGE.getRoute(reportID, transactionID, Navigation.getActiveRoute()));
  	}, [reportID, transactionID]);

 const handleDatePress = useCallback(() => {
        const splitExpenseRoute = ROUTES.SPLIT_EXPENSE.getRoute(reportID, transactionID, splitExpenseTransactionID, backTo);
        Navigation.navigate(ROUTES.SPLIT_EXPENSE_CREATE_DATE_RANGE.getRoute(reportID, transactionID, splitExpenseRoute));
    }, [reportID, transactionID, splitExpenseTransactionID, backTo]);

What alternative solutions did you explore? (Optional)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022011772098849633087

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @truph01 (External)

[nkdengineer]

Proposal

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

Split by date for 30 days shows skeleton and directs to workspace chat page.

What is the root cause of that problem?

After spliting expense, the user received a reconnect app event, and we call a full reconnect App here. With full reconnect app, a full set of app data will be returned, and it clears the expense report sometimes

App/src/libs/actions/User.ts

Lines 963 to 969 in 504a289

	PusherUtils.subscribeToMultiEvent(Pusher.TYPE.MULTIPLE_EVENT_TYPE.RECONNECT_APP, () => {
	reconnectApp();
	return Promise.resolve();
	});
	initializePusherPingPong();
	}

Then the skeleton appears, and we go back to the workspace chat here

App/src/pages/home/ReportScreen.tsx

Lines 750 to 763 in 504a289

	Navigation.dismissModal();
	if (Navigation.getTopmostReportId() === prevOnyxReportID) {
	Navigation.isNavigationReady().then(() => {
	Navigation.popToSidebar();
	});
	}
	if (prevReport?.parentReportID) {
	// Prevent navigation to the IOU/Expense Report if it is pending deletion.
	if (isMoneyRequestReportPendingDeletion(prevReport.parentReportID)) {
	return;
	}
	Navigation.isNavigationReady().then(() => {
	Navigation.navigate(ROUTES.REPORT_WITH_ID.getRoute(prevReport.parentReportID));
	});

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

We shouldn't perform a full reconnect app here, as it will return a full set of app data and cause the viewing data to be cleared. Instead, pass the lastUpdateID to handle partial reconnect app like here

let lastUpdateIDAppliedToClient: number | undefined;
Onyx.connectWithoutView({
    key: ONYXKEYS.ONYX_UPDATES_LAST_UPDATE_ID_APPLIED_TO_CLIENT,
    callback: (value) => (lastUpdateIDAppliedToClient = value),
});
PusherUtils.subscribeToMultiEvent(Pusher.TYPE.MULTIPLE_EVENT_TYPE.RECONNECT_APP, () => {
        reconnectApp(lastUpdateIDAppliedToClient);
        return Promise.resolve();
    });

App/src/libs/actions/User.ts

Lines 963 to 969 in 504a289

	PusherUtils.subscribeToMultiEvent(Pusher.TYPE.MULTIPLE_EVENT_TYPE.RECONNECT_APP, () => {
	reconnectApp();
	return Promise.resolve();
	});
	initializePusherPingPong();
	}

What alternative solutions did you explore? (Optional)

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[yatin-italy]

🚫 Duplicated proposal withdrawn by 🤖 ProposalPolice.

[github-actions]

⚠️ @yatin-italy Your proposal is a duplicate of an already existing proposal and has been automatically withdrawn to prevent spam. Please review the existing proposals before submitting a new one.