Skip to content

fix: navigate to Concierge chat after login from Concierge deep link on web - #96387

Open
x-dev90 wants to merge 31 commits into
Expensify:mainfrom
x-dev90:fix/web-concierge-deep-link-login-navigation
Open

fix: navigate to Concierge chat after login from Concierge deep link on web#96387
x-dev90 wants to merge 31 commits into
Expensify:mainfrom
x-dev90:fix/web-concierge-deep-link-login-navigation

Conversation

@x-dev90

@x-dev90 x-dev90 commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Preserve the /concierge deep-link intent when a logged-out user signs up with a new account, then consume that intent after onboarding before falling back to Home.

This keeps the existing pre-onboarding deep-link guard intact, avoids reopening stale non-Concierge deep links, and routes the user to the Concierge report when available. If the Concierge report ID is not ready yet, it navigates to ROUTES.CONCIERGE so ConciergePage can resolve the chat.

Fixed Issues

$ #95365
PROPOSAL: #95365 (comment)

Tests

Case 1: Original Flow

  1. Log out of the app
  2. Open /concierge directly in the browser
  3. Sign up with a brand-new account
  4. Complete onboarding
  5. Verify the Concierge chat opens

Additional Cases

  1. Log out of the app
  2. Open /concierge directly in the browser
  3. Start signup but do not complete onboarding
  4. In the same tab, navigate to /
  5. Sign up normally from /
  6. Complete onboarding
  7. Verify the app lands on Home and does not open Concierge

  1. Log out of the app
  2. Open /
  3. Sign up with a brand-new account
  4. Complete onboarding
  5. Verify the app follows the normal onboarding destination and does not open Concierge from stale state

  1. Log out of the app
  2. Open /concierge/
  3. Sign up with a brand-new account
  4. Complete onboarding
  5. Verify the Concierge chat opens

  1. Log out of the app
  2. Open /concierge?test=1
  3. Sign up with a brand-new account
  4. Complete onboarding
  5. Verify the Concierge chat opens

  1. Log out of the app
  2. Open /concierge#test
  3. Sign up with a brand-new account
  4. Complete onboarding
  5. Verify the Concierge chat opens
  • Verify that no errors appear in the JS console

Offline tests

Same as tests.

QA Steps

Same as tests.

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

  • 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 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.
  • 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
Screen_Recording_20260717_182305_Chrome.mp4
iOS: Native
iOS: mWeb Safari
Screen.Recording.2026-07-17.at.6.33.33.PM.mp4
MacOS: Chrome / Safari
Screen.Recording.2026-07-17.at.5.56.41.PM.mp4

@codecov

codecov Bot commented Jul 17, 2026

Copy link
Copy Markdown

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/DeepLinkHandler.tsx 86.79% <100.00%> (+0.25%) ⬆️
src/libs/actions/Link.ts 52.82% <100.00%> (+0.15%) ⬆️
src/libs/actions/SignInRedirect.ts 74.07% <100.00%> (+0.48%) ⬆️
src/libs/actions/Report/index.ts 71.47% <50.00%> (-0.12%) ⬇️
src/libs/navigateAfterOnboarding.ts 92.10% <96.55%> (+4.10%) ⬆️
src/hooks/useAutoCreateSubmitWorkspace.ts 86.95% <50.00%> (-7.79%) ⬇️
src/hooks/useAutoCreateTrackWorkspace.ts 82.92% <60.00%> (-3.56%) ⬇️
.../OnboardingWorkspaces/BaseOnboardingWorkspaces.tsx 95.06% <50.00%> (-2.35%) ⬇️
src/hooks/useCompleteOnboarding.ts 0.00% <0.00%> (ø)
src/libs/PendingConciergeDeepLink.ts 94.44% <94.44%> (ø)
... and 3 more
... and 9 files with indirect coverage changes

@x-dev90
x-dev90 marked this pull request as ready for review July 17, 2026 13:58
@x-dev90
x-dev90 requested review from a team as code owners July 17, 2026 13:58
@melvin-bot
melvin-bot Bot requested review from brunovjk and flaviadefaria July 17, 2026 13:58
@melvin-bot

melvin-bot Bot commented Jul 17, 2026

Copy link
Copy Markdown

@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 removed request for a team July 17, 2026 13:58
Comment thread src/libs/PendingConciergeDeepLink.ts

@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: f870138760

ℹ️ 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".

Comment thread src/libs/PendingConciergeDeepLink.ts
@x-dev90

x-dev90 commented Jul 18, 2026

Copy link
Copy Markdown
Contributor Author

Hi @brunovjk, I tested one additional edge case and would like to confirm the expected behavior.

Steps:

  1. Log out.
  2. Open /concierge.
  3. Before completing signup/onboarding, open /.
  4. Complete signup/onboarding.

I also tested this on main, and the app still navigates to Concierge after onboarding. So this behavior does not seem to be introduced by this PR.

My understanding is that the app currently preserves the original /concierge signup deep-link intent through onboarding, and visiting / before onboarding completes does not cancel it.

Could you please confirm how we should handle this? Should this PR keep the current main behavior and only fix the reported Concierge onboarding issue, or should we also update the behavior so opening / explicitly cancels the pending Concierge intent?

Tested on main:

Screencast.From.2026-07-18.22-40-19.mp4

@x-dev90

x-dev90 commented Jul 18, 2026

Copy link
Copy Markdown
Contributor Author

Hi @brunovjk, just following up on this PR.

I addressed the AI feedback by persisting the pending Concierge deep-link intent in sessionStorage, so it can survive a tab reload during signup/onboarding and still be cleared through the existing consume/sign-out paths.

Could you please review the latest changes when you have a chance?

@brunovjk

Copy link
Copy Markdown
Contributor

@x-dev90 It’s not very consistent, so I couldn't record a video, but it happens sometimes. If you access the deeplink with /concierge and—before entering the new acc—you go to / instead, causing a normal signup to open Concierge instead of Workspace settings page. I think this happens because / is a public route, so clearPendingConciergeDeepLink() isn’t called. Could you take a look and let me know what you think?

Also, If you enter using only the / deeplink, select "Something else" during onboarding, and complete the process, you are redirected to /concierge instead of Home:

Screen.Recording.2026-07-20.at.14.33.42.mov

@x-dev90

x-dev90 commented Jul 21, 2026

Copy link
Copy Markdown
Contributor Author

@x-dev90 It’s not very consistent, so I couldn't record a video, but it happens sometimes. If you access the deeplink with /concierge and—before entering the new acc—you go to / instead, causing a normal signup to open Concierge instead of Workspace settings page. I think this happens because / is a public route, so clearPendingConciergeDeepLink() isn’t called. Could you take a look and let me know what you think?

Also, If you enter using only the / deeplink, select "Something else" during onboarding, and complete the process, you are redirected to /concierge instead of Hom

Hi @brunovjk ,I updated the implementation to preserve the pending /concierge intent across page reloads using tab-scoped sessionStorage, while still allowing an explicit root/Home navigation to cancel that intent. I also handled generated root/Home startup events so they do not incorrectly override an existing pending Concierge intent.

I added focused unit coverage for the Concierge redirect, explicit root cancellation, direct root signup, and reload cases. I also adjusted the reload detection to avoid direct deprecated API access.

Could you please review again when you have a chance?

Thank you!

After Fix:

Screencast.From.2026-07-22.01-34-13.mp4
Screencast.From.2026-07-22.01-31-38.mp4
Screencast.From.2026-07-22.01-36-26.mp4
Screencast.From.2026-07-22.01-37-43.mp4

@brunovjk

Copy link
Copy Markdown
Contributor

Thanks for the effort @x-dev90, but now it seems to be failing on the initial issue:

Screen.Recording.2026-07-22.at.13.38.18.mov

@x-dev90

x-dev90 commented Jul 25, 2026

Copy link
Copy Markdown
Contributor Author

Hi @brunovjk, could you please review this PR again when you have a chance?

After the previous approval, I found and addressed a few remaining edge cases. The earlier fix covered refreshing before signup after opening the deep link, but the latest updates also cover refreshes during and after signup while onboarding is still in progress.

The PR now preserves the original /concierge deep-link intent across those signup/onboarding refresh flows. It also makes the Submit workspace onboarding flow honor the same pending intent instead of incorrectly navigating to Workspace settings, #admins, or Home.

I also addressed the two-tab sync case: if /concierge is opened in one tab, but the user later opens / or another explicit internal route in another tab before completing onboarding, the stale Concierge intent is cancelled across tabs so both tabs stay aligned with the latest user intent.

I added focused unit coverage for these cases as well. Could you please take another look?

Before

Screencast.From.2026-07-25.15-57-36.mp4
Screencast.From.2026-07-25.16-04-16.mp4
vokoscreenNG-2026-07-25_01-00-50.mp4

After Fix:

Screencast.From.2026-07-25.16-18-52.mp4
Screencast.From.2026-07-25.15-12-55.mp4
Screencast.From.2026-07-25.16-20-49.mp4

@x-dev90
x-dev90 requested a review from brunovjk July 25, 2026 11:57
@x-dev90

x-dev90 commented Jul 26, 2026

Copy link
Copy Markdown
Contributor Author

@x-dev90 please ping me when this is on me

Hi @cristipaval, thanks for waiting.

I’ve finished the additional testing and addressed the remaining edge cases, including refresh during onboarding, Submit workspace onboarding, and two-tab intent sync. This should be ready for you once @brunovjk re-reviews the latest changes.

@x-dev90

x-dev90 commented Jul 27, 2026

Copy link
Copy Markdown
Contributor Author

@brunovjk Gentle bump when you have a chance. Thanks!

@brunovjk

Copy link
Copy Markdown
Contributor

@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: a5eb8b0f94

ℹ️ 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".

Comment thread src/libs/PendingConciergeDeepLink.ts Outdated
Comment on lines +214 to +216
} else if (normalizedRoute === '/') {
// Root is an explicit normal signup intent, so it cancels Concierge unless it is a reload replay.
setPendingHomeDeepLinkForRoot();

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Only store Home when replacing a pending Concierge intent

For an ordinary logged-out web load at /, openReportFromDeepLink() reaches this branch even when no Concierge intent exists, so it creates a pending Home flag. When onboarding finishes, navigateToPendingDeepLinkAfterOnboarding() consumes that flag and returns before the normal RHP variant, admin-room, or workspace navigation runs. Consequently, normal signups from the root URL are forced to Home instead of following their existing onboarding destination; the Home marker should only be created when it is actually canceling a pending Concierge intent.

Useful? React with 👍 / 👎.

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.

Hi @brunovjk, thank you for taking the time to review this.

I tested the fresh / signup flow on main, without opening /concierge first. On main, opening /, signing up, and completing onboarding navigates to Concierge. I also added an extra fix in this PR so / -> signup/onboarding now lands on Home instead of Concierge.

This PR now fixes both related flows:

  • /concierge -> signup/onboarding preserves the Concierge intent.
  • / -> signup/onboarding lands on Home instead of Concierge.

I also re-tested the other onboarding flows, and they continue to behave as expected.

Could you please confirm if this is the behavior we want to keep?

Comment on lines +168 to +170
// Submit workspace onboarding bypasses navigateAfterOnboarding(), so honor the same pending deep-link intent here.
if (navigateToPendingDeepLinkAfterOnboarding(conciergeReportID)) {
return;

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 Avoid consuming onboarding intents from the Submit welcome modal

When an existing user signs in through /concierge, the normal deep-link handler opens Concierge but never consumes the new pending flag because no onboarding completion occurs. If that user then confirms the proactively shown SubmitPlanWelcomeModal, its shouldCompleteOnboarding=false path still reaches this check, consumes the stale flag, and returns before navigating to Workspace Categories or opening the side panel. Restrict this pending-intent handling to actual onboarding callers, or clear the intent after it has been fulfilled for an already-onboarded sign-in.

Useful? React with 👍 / 👎.

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.

@brunovjk, thanks for checking this.

I tested the existing-user sign-in flow separately, but I could not reproduce the issue. Signing in through /concierge opens Concierge as expected, and confirming the SubmitPlanWelcomeModal still navigates to Workspace Categories with the side panel open.

Since the sign-in flow works separately from the signup/onboarding flow covered by this PR, I’m not seeing the stale pending intent issue described here. Could you please confirm if there are specific steps I should test?

@brunovjk

brunovjk commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

@x-dev90 what do you think about the comments (P1 and P2) above? We also have some conflicts.Thanks.

@x-dev90

x-dev90 commented Jul 28, 2026

Copy link
Copy Markdown
Contributor Author

@brunovjk, could you please check this when you get a chance. thanks.

@brunovjk

Copy link
Copy Markdown
Contributor

Great work, @x-dev90. However, the Home screen opens first, briefly, and then the concierge page opens a moment later.

Screen.Recording.2026-07-28.at.11.12.54.mov

Do you think we can fix this? Thanks.

@x-dev90

x-dev90 commented Jul 30, 2026

Copy link
Copy Markdown
Contributor Author

Great work, @x-dev90. However, the Home screen opens first, briefly, and then the concierge page opens a moment later.

Hi @brunovjk , I’ve addressed the feedback. Could you please review again?

@brunovjk

Copy link
Copy Markdown
Contributor

@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: e2adfa85d5

ℹ️ 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".

Comment thread src/libs/navigateAfterOnboarding.ts
@x-dev90

x-dev90 commented Jul 30, 2026

Copy link
Copy Markdown
Contributor Author

Hi @brunovjk, thank you for taking the time to review this!

I've added one final fix for the / signup flow. Although this flow wasn't mentioned in the original issue, it always shows Concierge after onboarding on the main branch. After the previous fix, it still briefly showed Concierge before navigating to the correct onboarding target page. With this change, it now navigates directly to the expected onboarding target page without showing Concierge first.

Test steps:

  1. Open https://dev.new.expensify.com:8082/.
  2. Sign up and complete onboarding.
  3. Verify you're taken directly to the expected onboarding target page without briefly seeing Concierge.

Since this is closely related to the same post-onboarding routing behavior, I think it makes sense to keep it in this PR. Could you please take another look and let me know if this approach looks good?

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.

3 participants