You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[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
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
👋 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:
Identify the pull request that introduced this issue and revert it.
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.
@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]
[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
Activity
github-actions commentedon Aug 18, 2025
👋 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:
melvin-bot commentedon Aug 18, 2025
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 commentedon Aug 18, 2025
Triggered auto assignment to @pecanoro (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Aug 18, 2025
💬 A slack conversation has been started in #expensify-open-source
samranahm commentedon Aug 18, 2025
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
What changes do you think we should make in order to solve the problem?
we should use navigation ready here
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.
35 remaining items
melvin-bot commentedon Oct 8, 2025
@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]
ishpaul777 commentedon Oct 9, 2025
👋 can we please reopen and assign me here,i reviewed #71367
@pecanoro @sonialiap
ishpaul777 commentedon Oct 14, 2025
gentle bump @pecanoro 🙇
pecanoro commentedon Oct 14, 2025
@sonialiap We need payment for @ishpaul777
melvin-bot commentedon Oct 15, 2025
Payment Summary
Upwork Job
BugZero Checklist (@sonialiap)
sonialiap commentedon Oct 15, 2025
Payment summary:
ishpaul777 commentedon Oct 16, 2025
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
sonialiap commentedon Oct 17, 2025
Thanks!
garrettmknight commentedon Nov 11, 2025
$250 approved for @ishpaul777