[Due for payment 2025-10-15] [Due for payment 2025-08-29] "'navigation' object hasn't been initialized yet" console error when logging in

[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.1.96-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #68530
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: Windows 10 / Chrome
App Component: Other

Action Performed:

1. Navigate to https://staging.new.expensify.com/ in Chrome incognito with the console open
2. Log in with a new Gmail account

Expected Result:

Console error shouldn't be visible.

Actual Result:

"'navigation' object hasn't been initialized yet" console error when logging in with a new Gmail account.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

logs.txt

1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @ishpaul777

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

Triggered auto assignment to @sonialiap (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.

[melvin-bot]

Triggered auto assignment to @pecanoro (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[samranahm]

Proposal

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

navigation' object hasn't been initialized yet" console error when logging in

What is the root cause of that problem?

we are calling the useEffect too early here

App/src/components/SidePanel/useSyncSidePanelWithHistory/index.ts

Lines 15 to 27 in 6e467dc

	useEffect(() => {
	// If the window width has been expanded and the modal is displayed, remove its history entry.
	// The side panel is only synced with the history when it's displayed as RHP.
	if (!shouldHideSidePanel && isExtraLargeScreenWidth) {
	navigationRef.dispatch({
	type: CONST.NAVIGATION.ACTION_TYPE.TOGGLE_SIDE_PANEL_WITH_HISTORY,
	payload: {isVisible: false},
	});
	return;
	}
	// When shouldHideSidePanel changes, synchronize the side panel with the browser history.
	navigationRef.dispatch({

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

we should use navigation ready here

if (navigationRef.isReady()) {
    navigationRef.dispatch({
        type: CONST.NAVIGATION.ACTION_TYPE.TOGGLE_SIDE_PANEL_WITH_HISTORY,
        payload: {isVisible: !shouldHideSidePanel},
    });
}

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

N/A

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.