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
Onboarding - User redirected to first modal after page reload #80852
Version Number: v9.3.11-1 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack:https://test-management.browserstack.com/projects/2219752/folder/13176677/test-cases/41237662 Email or phone of affected tester (no customers): N/A Issue reported by: Applause Internal Team Bug source: Regression TC Execution Device used: Windows 11, 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.
Classification: Frontend bug Causing PR: Unable to determine with high confidence - appears to be a pre-existing issue or race condition Related Issues: None found
Recommendation: NEEDS INVESTIGATION
The issue requires deeper investigation by the onboarding flow experts to identify the root cause.
Labels: Keeping DeployBlockerCash (App deploy is blocked)
Detailed Analysis
Evidence
The bug occurs when a user refreshes the page during onboarding at the "Do you use any accounting software?" step. After refresh, they are redirected to the first onboarding page instead of staying on the current page.
Code Analysis
The onboarding flow uses ONBOARDING_LAST_VISITED_PATH (stored in Onyx) to track the user's current position in the onboarding flow. On page refresh:
NavigationRoot.tsxinitialState logic (line 141) checks if onboarding is incomplete
Calls getOnboardingInitialPath() with the stored path and onboarding state
getOnboardingInitialPath() validates the stored path and returns where to navigate
The issue appears to be that on page refresh, one of these scenarios occurs:
ONBOARDING_LAST_VISITED_PATH is not persisted or loaded correctly
Onboarding state values (currentOnboardingCompanySize, currentOnboardingPurposeSelected) are not available when getOnboardingInitialPath() runs
The validation logic in getOnboardingInitialPath() (line 151-164) incorrectly determines the path is invalid
Investigation Attempts
Searched staging deploy PRs for onboarding-related changes: No direct modifications found
cc @szymonzalarski98 as you are an author of the PR that caused it, could you please take action on that? To avoid reverting the PR I'd suggest getting rid of Log
Activity
melvin-bot commentedon Jan 29, 2026
Triggered auto assignment to @stitesExpensify (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jan 29, 2026
Triggered auto assignment to @CortneyOfstad (
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 Jan 29, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jan 29, 2026
👋 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:
OSBotify commentedon Jan 29, 2026
Investigation Summary
Classification: Frontend bug
Causing PR: Unable to determine with high confidence - appears to be a pre-existing issue or race condition
Related Issues: None found
Recommendation: NEEDS INVESTIGATION
The issue requires deeper investigation by the onboarding flow experts to identify the root cause.
Labels: Keeping
DeployBlockerCash(App deploy is blocked)Detailed Analysis
Evidence
The bug occurs when a user refreshes the page during onboarding at the "Do you use any accounting software?" step. After refresh, they are redirected to the first onboarding page instead of staying on the current page.
Code Analysis
The onboarding flow uses
ONBOARDING_LAST_VISITED_PATH(stored in Onyx) to track the user's current position in the onboarding flow. On page refresh:NavigationRoot.tsxinitialStatelogic (line 141) checks if onboarding is incompletegetOnboardingInitialPath()with the stored path and onboarding stategetOnboardingInitialPath()validates the stored path and returns where to navigateThe issue appears to be that on page refresh, one of these scenarios occurs:
ONBOARDING_LAST_VISITED_PATHis not persisted or loaded correctlycurrentOnboardingCompanySize,currentOnboardingPurposeSelected) are not available whengetOnboardingInitialPath()runsgetOnboardingInitialPath()(line 151-164) incorrectly determines the path is invalidInvestigation Attempts
Root Cause Hypothesis
This appears to be either:
getOnboardingInitialPath()executes on page refreshWhy This is a Frontend Bug
NavigationRoot.tsx,OnboardingFlow.ts, or Onyx state persistenceNext Steps:
TMisiukiewicz commentedon Jan 29, 2026
I already described the root cause here: #79898 (comment)
It was introduced in #79073
cc @szymonzalarski98 as you are an author of the PR that caused it, could you please take action on that? To avoid reverting the PR I'd suggest getting rid of
Logszymonzalarski98 commentedon Jan 29, 2026
@TMisiukiewicz sure, on it
szymonzalarski98 commentedon Jan 29, 2026
Here is the PR with fix: #80870
mountiny commentedon Jan 30, 2026
#79073 was reverted
mountiny commentedon Jan 30, 2026
https://expensify.slack.com/archives/C09V78U42D8/p1769732499166289 asked for a retest
m-natarajan commentedon Jan 30, 2026
Issue no longer reproducible , Retested on Windows 11 / Chrome. Build 9.3.11-12
Accounting.mp4