Skip to content

Create Navigation guards with OnboardingGuard & TestDriveModalGuard#81689

Merged
mountiny merged 10 commits intoExpensify:mainfrom
callstack-internal:navigation-guards-v2
Feb 12, 2026
Merged

Create Navigation guards with OnboardingGuard & TestDriveModalGuard#81689
mountiny merged 10 commits intoExpensify:mainfrom
callstack-internal:navigation-guards-v2

Conversation

@TMisiukiewicz
Copy link
Copy Markdown
Contributor

@TMisiukiewicz TMisiukiewicz commented Feb 6, 2026

Explanation of Change

Fixed Issues

$ #79974
$ #81453
PROPOSAL:

Tests

  1. Create fresh account
  2. Verify you are navigated to onboarding
  3. Go through entire onboarding
  4. Verify the test drive modal appears

  1. Create fresh account
  2. Verify you are navigated to onboarding
  3. Close the app
  4. Web: Open https://dev.new.expensify.com:8082/workspaces
  5. iOS: run xcrun simctl openurl booted "new-expensify://workspaces" in terminal
  6. Android: run adb shell am start -W -a android.intent.action.VIEW -d "new-expensify://workspaces"
  7. Verify you are redirected to the onboarding

  1. Create fresh account
  2. Verify you are navigated to onboarding
  3. Do the first step of the onboarding
  4. Close the app
  5. Web: Open https://dev.new.expensify.com:8082/workspaces
  6. iOS: run xcrun simctl openurl booted "new-expensify://workspaces" in terminal
  7. Android: run adb shell am start -W -a android.intent.action.VIEW -d "new-expensify://workspaces"
  8. Verify you are redirected to the last visited onboarding step

  1. Create fresh account
  2. Verify you are navigated to onboarding
  3. Do the first step of the onboarding
  4. Close the app
  5. Web: Open https://dev.new.expensify.com:8082/onboarding/purpose
  6. iOS: run xcrun simctl openurl booted "new-expensify://onboarding/purpose" in terminal
  7. Android: run adb shell am start -W -a android.intent.action.VIEW -d "new-expensify://onboarding/purpose"
  8. Verify you are redirected to the personal details step

  1. Create fresh account
  2. Verify you are navigated to onboarding
  3. Go through entire onboarding
  4. In the console:
Onyx.set("nvp_tryNewDot", {classicRedirect: {dismissed: false}, nudgeMigration: {timestamp: 
"2025-12-10 01:35:12", cohort: "test"}});
  1. Reopen the app
  2. Verify you are navigated to "Welcome to New Expensify" modal

  1. Create a fresh account
  2. Complete the entire onboarding flow (name, email, purpose, etc.)
  3. Verify the test drive modal appears automatically
  4. Close it
  5. Verify it did not reappear

  1. Create a fresh account
  2. Complete the entire onboarding flow
  3. Wait for test drive modal to appear
  4. Dismiss the modal (click "Skip" or close button)
  5. Navigate to different tabs (Workspaces, Settings, etc.)
  6. Verify the modal does NOT reappear

  1. Create a fresh account
  2. Complete onboarding and dismiss the test drive modal
  3. Manually navigate to /onboarding/workspaces by:
    • Web: Type URL in address bar
    • iOS: xcrun simctl openurl booted "newexpensify://workspaces"
    • Android: adb shell am start -a android.intent.action.VIEW -d "newexpensify://workspaces"
  4. Verify you're redirected to Test drive modal
  5. Close it
  6. Verify the modal does not reappear
  • Verify that no errors appear in the JS console

Offline tests

n/a

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."
Same as tests

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
android.mov
Android: mWeb Chrome
iOS: Native
ios.mov
iOS: mWeb Safari
ios.web.mov
MacOS: Chrome / Safari
web.mov

@codecov
Copy link
Copy Markdown

codecov Bot commented Feb 6, 2026

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/hooks/useOnboardingFlow.ts 87.50% <100.00%> (+0.40%) ⬆️
src/libs/Navigation/NavigationRoot.tsx 76.92% <ø> (-0.86%) ⬇️
src/libs/Navigation/guards/OnboardingGuard.ts 100.00% <100.00%> (ø)
src/libs/Navigation/guards/index.ts 100.00% <100.00%> (ø)
src/libs/actions/Link.ts 22.70% <100.00%> (-0.62%) ⬇️
src/libs/actions/Welcome/index.ts 40.67% <ø> (-1.75%) ⬇️
src/libs/navigateAfterOnboarding.ts 70.37% <100.00%> (+1.40%) ⬆️
.../pages/OnboardingPurpose/BaseOnboardingPurpose.tsx 2.85% <ø> (ø)
src/Expensify.tsx 84.10% <50.00%> (-0.25%) ⬇️
src/libs/Navigation/guards/TestDriveModalGuard.ts 96.42% <96.42%> (ø)
... and 1 more
... and 13 files with indirect coverage changes

@TMisiukiewicz TMisiukiewicz marked this pull request as ready for review February 9, 2026 13:19
@TMisiukiewicz TMisiukiewicz requested review from a team as code owners February 9, 2026 13:19
@melvin-bot melvin-bot Bot requested review from JmillsExpensify and brunovjk and removed request for a team February 9, 2026 13:19
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Feb 9, 2026

@brunovjk Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot melvin-bot Bot requested review from a team, QichenZhu and mountiny and removed request for a team February 9, 2026 13:19
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Feb 9, 2026

@QichenZhu @mountiny One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@TMisiukiewicz
Copy link
Copy Markdown
Contributor Author

@eh2077 You might be interested in reviewing this once again since you already have some context from the 1st PR

Comment thread src/libs/Navigation/guards/OnboardingGuard.ts
@TMisiukiewicz
Copy link
Copy Markdown
Contributor Author

not sure why lint fails, it finished with 0 errors

@mountiny mountiny requested review from eh2077 and removed request for QichenZhu and brunovjk February 9, 2026 13:39
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 9, 2026

🚧 @mountiny has triggered a test Expensify/App build. You can view the workflow run here.

@github-actions

This comment has been minimized.

@eh2077
Copy link
Copy Markdown
Contributor

eh2077 commented Feb 9, 2026

I'll look into it tmr

@TMisiukiewicz
Copy link
Copy Markdown
Contributor Author

@eh2077 I was able to reproduce and provided a fix that should prevent this issue in the future, could you please take a look? 🙏

Copy link
Copy Markdown
Contributor

@eh2077 eh2077 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

works well!

Screen.Recording.2026-02-11.at.6.19.09.PM.mov
Screen.Recording.2026-02-11.at.6.32.33.PM.mov

mountiny
mountiny previously approved these changes Feb 11, 2026
@mountiny mountiny merged commit f065af6 into Expensify:main Feb 12, 2026
30 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

🚧 @mountiny has triggered a test Expensify/App build. You can view the workflow run here.

@github-actions
Copy link
Copy Markdown
Contributor

@OSBotify
Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/mountiny in version: 9.3.18-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@vincdargento
Copy link
Copy Markdown

@TMisiukiewicz It's the last test ok?

  1. Create a fresh account
  2. Complete onboarding and dismiss the test drive modal
  3. Manually navigate to /onboarding/workspaces by:
  • Web: Type URL in address bar
  • iOS: xcrun simctl openurl booted "newexpensify://workspaces"
  • Android: adb shell am start -a android.intent.action.VIEW -d "newexpensify://workspaces"
  1. Verify you're redirected to Test drive modal
  2. Close it
  3. Verify the modal does not reappear

Navigating to /onboarding/workspaces after completing the onboarding and dismissing the test drive modal it's leading to Not here page, but I feel this is expected, I just want to confirm

test.seven.faile.mp4

@TMisiukiewicz
Copy link
Copy Markdown
Contributor Author

Hello @vincdargento ! I'm sorry, there is a mistake in the test plan 🙏 The correct version:

  1. Create a fresh account
  2. Complete onboarding and DO NOT dismiss the test drive modal
  3. Manually navigate to /workspaces by:
  • Web: Type URL in address bar
  • iOS: xcrun simctl openurl booted "newexpensify://workspaces"
  • Android: adb shell am start -a android.intent.action.VIEW -d "newexpensify://workspaces"
  1. Verify you're redirected to Test drive modal
  2. Close it
  3. Verify the modal does not reappear

Thank you for reporting this! 🙏

@IuliiaHerets
Copy link
Copy Markdown

@TMisiukiewicz QA team got this error:

Starting: Intent { act=android.intent.action.VIEW dat=new-expensify://workspaces/... } Error: Activity not started, unable to resolve Intent { act=android.intent.action.VIEW dat=new-expensify://workspaces/... flg=0x10000000 }

when run the step

  1. run adb shell am start -W -a android.intent.action.VIEW -d "new-expensify://workspaces"

Can we skip this test? or any workaround to make it work?

bandicam.2026-02-13.15-09-44-447.mp4

@TMisiukiewicz
Copy link
Copy Markdown
Contributor Author

@IuliiaHerets not sure how to fix that, I think it's safe to skip this test

@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/lakchote in version: 9.3.18-8 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

// eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing
const isInvitedOrGroupMember = (!CONFIG.IS_HYBRID_APP && (hasNonPersonalPolicy || wasInvitedToNewDot)) ?? false;

const shouldSkipOnboarding = context.isLoading || isTransitioning || isOnboardingCompleted || isMigratedUser || isSingleEntry || needsExplanationModal || isInvitedOrGroupMember;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The onboarding guard added in this PR caused critical bug in onboarding flow.
Infinite loop, which leads to crash

More details: #83212 (comment)

Navigation.navigate(ROUTES.REPORT_WITH_ID.getRoute(reportID));
} else {
// Navigate to home to trigger guard evaluation
Navigation.navigate(ROUTES.HOME);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@TMisiukiewicz Looks like we don't have the test drive modal guard anymore, do we still need it?

After completing the onboarding, this always navigate the user to HOME instead of staying where they were.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if this was here only to satisfy the test drive modal then it should be safe to remove 👍

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants