Skip to content

Fix: onboarding Track-business users land on Home instead of Inbox - #97841

Draft
marcochavezf wants to merge 2 commits into
mainfrom
claude-onboardingTrackBusinessInbox-v2
Draft

Fix: onboarding Track-business users land on Home instead of Inbox#97841
marcochavezf wants to merge 2 commits into
mainfrom
claude-onboardingTrackBusinessInbox-v2

Conversation

@marcochavezf

@marcochavezf marcochavezf commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

After a user completes onboarding with "Track expenses for my business," navigateAfterOnboarding() and handleRHPVariantNavigation() can leave the user on an empty Inbox. The onboarding guards call isReportTopmostSplitNavigator(), which checks only whether the Reports tab is topmost. A topmost Reports tab can contain only the Inbox sidebar, so the guard skips Navigation.navigate(ROUTES.HOME) even though no report is open.

This PR adds isReportRevealedInTopmostSplitNavigator(). It checks the topmost Reports split navigator's inner routes for SCREENS.REPORT and uses preserved navigator state when onboarding has removed the live state before the check. The three onboarding call sites now use this helper. Regression tests cover the RHP variants and the larger-screen onboarding path, including preserving a report when one is revealed.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/663126
PROPOSAL: https://github.com/Expensify/Expensify/issues/663126#issuecomment-5074382682

Tests

Automated coverage checks both onboarding navigation paths. RHPVariantTest.test.ts covers the RHP variants when no report is revealed, and navigateAfterOnboardingTest.ts adds the larger-screen case where the Reports tab contains only the Inbox while retaining coverage for a revealed report.

Offline tests

N/A. This change only reads local navigation state.

QA Steps

  • Create a new account and start onboarding.
  • Select "Track expenses for my business," complete onboarding, and confirm Home opens instead of Inbox.
  • Repeat the flow to cover the case where Inbox is the base tab.
  • Open a report before onboarding completes and confirm it remains open after onboarding on small and large screens.
  • 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 followed proper code patterns (see Reviewing the code)
    • 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 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)
  • 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)
  • 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 these 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.
  • 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: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

The guard at the onboarding call sites used isReportTopmostSplitNavigator(),
which only checks whether the Reports tab is topmost, not whether it
actually shows a report. When a fresh onboarding user's base tab happened
to be the empty Inbox, the guard treated that as a report worth preserving
and skipped Navigation.navigate(ROUTES.HOME), leaving the user stranded on
Inbox.

Adds isReportRevealedInTopmostSplitNavigator() in
src/libs/Navigation/helpers/, which also requires a SCREENS.REPORT route in
the split's inner routes before treating it as revealed. Replaces the guard
at both call sites in RHPVariantTest/index.ts and navigateAfterOnboarding.ts.
isReportTopmostSplitNavigator is left untouched, since IOU flows and
SignInModal still call it directly for unrelated checks.

Fixes Expensify/Expensify#663126

Recreated from #97009 on a clean branch off main. #97009's branch had
ingested unrelated, still-in-progress commits from a separate PR
(#96508, Concierge optimistic reveal cadence) through repeated cross-branch
merges, so this is the same change isolated from that entanglement rather
than a new fix.
@codecov

codecov Bot commented Aug 4, 2026

Copy link
Copy Markdown

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/components/SidePanel/RHPVariantTest/index.ts 51.51% <100.00%> (ø)
src/libs/navigateAfterOnboarding.ts 88.00% <100.00%> (ø)
...helpers/isReportRevealedInTopmostSplitNavigator.ts 66.66% <66.66%> (ø)
... and 206 files with indirect coverage changes

@marcochavezf

Copy link
Copy Markdown
Contributor Author

(Marco's agent): @codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bb4ddf44a8

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

const innerRoutes: ReadonlyArray<{name: string}> | undefined =
topmostFullScreenRoute.state?.routes ?? (topmostFullScreenRoute.key ? getPreservedNavigatorState(topmostFullScreenRoute.key)?.routes : undefined);

return !!innerRoutes?.some((route) => route.name === SCREENS.REPORT);

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Require a real report before preserving Inbox

When the active Reports split has already mounted on a wide layout from /inbox, the split router injects its default central SCREENS.REPORT route even when no chat/report is selected, and that placeholder can have an empty or missing reportID. This check treats that placeholder exactly like a revealed report, so the Track-business/RHP onboarding paths skip Navigation.navigate(ROUTES.HOME) and can still leave the user on the empty Inbox instead of Home; please only preserve when the Report route has a non-empty report ID (or otherwise distinguish the placeholder route).

Useful? React with 👍 / 👎.

@marcochavezf

Copy link
Copy Markdown
Contributor Author

(Marco's agent): @claude review

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.

1 participant