Skip to content

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

Closed

Description

@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 OwnerCurrent Issue Owner: @ishpaul777

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Aug 18, 2025
  2. github-actions commented on Aug 18, 2025

    @github-actions
    Contributor

    👋 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.
  3. melvin-bot commented on Aug 18, 2025

    @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.

  4. melvin-bot commented on Aug 18, 2025

    @melvin-bot

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

  5. melvin-bot commented on Aug 18, 2025

    @melvin-bot

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

  6. samranahm commented on Aug 18, 2025

    @samranahm
    Contributor

    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

    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.

  7. added
    ReviewingHas a PR in review
    and removed on Aug 19, 2025
  8. 35 remaining items

  9. melvin-bot commented on Oct 8, 2025

    @melvin-bot

    @pecanoro @sonialiap @WojtekBoman The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  10. ishpaul777 commented on Oct 9, 2025

    @ishpaul777
    Contributor

    👋 can we please reopen and assign me here,i reviewed #71367

    @pecanoro @sonialiap

  11. ishpaul777 commented on Oct 14, 2025

    @ishpaul777
    Contributor

    gentle bump @pecanoro 🙇

  12. pecanoro commented on Oct 14, 2025

    @pecanoro
    Contributor

    @sonialiap We need payment for @ishpaul777

  13. melvin-bot commented on Oct 15, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    • Contributor: @WojtekBoman is from an agency-contributor and not due payment
    • Reviewer: @ishpaul777 owed $250 via NewDot

    BugZero Checklist (@sonialiap)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  14. sonialiap commented on Oct 15, 2025

    @sonialiap
    Contributor

    Payment summary:

  15. ishpaul777 commented on Oct 16, 2025

    @ishpaul777
    Contributor

    BugZero Checklist:

    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to comment: This was not a user facing bug introduced by single pr

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: no need

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again. not required

  16. sonialiap commented on Oct 17, 2025

    @sonialiap
    Contributor

    Thanks!

  17. garrettmknight commented on Nov 11, 2025

    @garrettmknight
    Contributor

    $250 approved for @ishpaul777

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions