Skip to content

Reapply opening a deep link captured before onboarding, without the Concierge regressions - #103681

Merged
pecanoro merged 9 commits into
Expensify:mainfrom
mukhrr:fix/99940-v2
Oct 17, 2026
Merged

pecanoro merged 9 commits into
Expensify:mainfrom
mukhrr:fix/99940-v2

Conversation

@mukhrr

@mukhrr mukhrr commented Oct 11, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

A deep link opened before signing up was dropped once the new account finished onboarding, and the earlier fix was reverted because replaying a /concierge link briefly showed the Concierge page's loading skeleton. This reapplies that fix, opens a replayed /concierge link directly in the chat, and stops the Concierge page from redirecting while onboarding is still open, which on Android closed onboarding early.

Fixed Issues

$ #99940
$ #102954
$ #102956
PROPOSAL: #99940 (comment)

Tests

You need email addresses that have never been used to sign up.

  1. Sign out so you land on the sign-in page.
  2. In the browser address bar, append /concierge to the app URL and load it.
  3. Enter an unused email address, click Continue, then click Join.
  4. Choose "Submit expenses to my employer" and finish onboarding.
  5. Verify the Concierge chat opens when onboarding finishes, with no Concierge loading panel sliding in first.
  6. On Android, sign out and open a /concierge app link so it opens in the app.
  7. Sign up with another unused email address, and when the notifications prompt appears, tap "Don't allow".
  8. Verify onboarding stays open instead of being replaced by the Concierge chat.
  9. Finish onboarding and verify the Concierge chat opens.

Note

The deep link is held in memory only, so refreshing the page during onboarding drops it and onboarding ends on the default destination instead of the Concierge chat. This is expected and not a regression.

  • Verify that no errors appear in the JS console

Offline tests

Completing onboarding writes optimistically, so the parked route is replayed from client state.

  1. Follow steps 1 to 4 above, disabling the network before finishing onboarding.
  2. Verify the Concierge chat still opens when onboarding completes.
  3. Re-enable the network and verify the app does not navigate a second time.

QA Steps

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 any copy / text that was added to the app 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 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 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 the Expensify/design team so the design team can review the changes.
  • If the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • 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
android.mp4
iOS: Native
iOS: mWeb Safari
ios.mWeb.mp4
MacOS: Chrome / Safari
web1.mp4

…ing it"

This reverts commit 4e385e2, bringing back Expensify#101558 unchanged. The
regressions that caused the revert are fixed in the next commit.
A parked /concierge link was replayed by navigating to the concierge route,
a URL entry page that shows a skeleton and redirects itself. On wide layouts
it slid in as a panel for close to a second after onboarding. The replay now
opens the chat with navigateToConciergeChat, as the rest of the app does.

When the app starts on /concierge for an account that has not finished
onboarding, ConciergePage mounts under the onboarding modal, and its
redirect dismisses the top modal, closing onboarding early. It now waits
until guided setup is complete.
@mukhrr
mukhrr requested review from a team as code owners October 11, 2026 06:32
@melvin-bot
melvin-bot Bot requested review from a team, QichenZhu, eh2077 and flaviadefaria and removed request for a team October 11, 2026 06:32
@melvin-bot

melvin-bot Bot commented Oct 11, 2026

Copy link
Copy Markdown

@eh2077 @QichenZhu 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]

@github-actions

Copy link
Copy Markdown
Contributor

This PR adds a new Onyx.connectWithoutView call, so I've requested a review from the Onyx performance reviewers (@tgolen, @mountiny, @luacmartins, @chuckdries) — a review from any one of them is enough. Please add a link in your PR description to the Slack discussion where the @frontend-performance team approved using connectWithoutView here.

@melvin-bot
melvin-bot Bot requested a review from trjExpensify October 11, 2026 06:32
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 11, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-11T06:50:45.525341Z bbb8e80 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@melvin-bot
melvin-bot Bot removed the request for review from a team October 11, 2026 06:32
@codecov

codecov Bot commented Oct 11, 2026 •

Copy link
Copy Markdown

Codecov Report

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

Files with missing lines Coverage Δ
src/pages/ConciergePage.tsx 94.59% <100.00%> (+94.59%) ⬆️
src/libs/navigateAfterOnboarding.ts 91.78% <94.11%> (+0.70%) ⬆️
src/libs/actions/Link.ts 68.35% <91.89%> (+8.75%) ⬆️
... and 284 files with indirect coverage changes

Tests openReportFromDeepLink's onboarding path: the link is parked instead of opened under onboarding, replayed only after report data loads, opened in the Concierge chat for /concierge, held until a linked report arrives, and dropped for links the app never replays.

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

ℹ️ 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/pages/ConciergePage.tsx
Comment thread src/libs/actions/Link.ts Outdated
Comment thread tests/unit/navigateAfterOnboardingTest.ts
The Concierge page waited for the onboarding flag, but workspace members,
invited users and other accounts the app never sends to onboarding keep
that flag false, so the page stayed on its skeleton. Keep waiting only
while onboarding can actually open.

Match the parked Concierge link by its parsed route so concierge/ and
concierge?x=1 also open the chat directly, and add the missing When/Then
comments to the parked link tests.
chuckdries
chuckdries previously approved these changes Oct 12, 2026

@chuckdries chuckdries left a comment

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.

I approve these connectWithoutView uses. Though, since they're one-shot reads that disconnect themselves, they're prime candidates for using Onyx.get on the off chance that #102135 lands first

@mountiny
mountiny removed their request for review October 12, 2026 16:03
@trjExpensify
trjExpensify removed their request for review October 12, 2026 21:12
@eh2077

eh2077 commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified any copy / text that was added to the app 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 verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • 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 the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
Screen.Recording.2026-10-15.at.8.56.29.PM.mov
Android: mWeb Chrome
Screen.Recording.2026-10-15.at.8.49.04.PM.mov
iOS: HybridApp
Screen.Recording.2026-10-15.at.8.54.22.PM.mov
iOS: mWeb Safari
Screen.Recording.2026-10-15.at.8.50.05.PM.mov
MacOS: Chrome / Safari
Screen.Recording.2026-10-15.at.8.46.18.PM.mov

luacmartins
luacmartins previously approved these changes Oct 13, 2026
@mukhrr

mukhrr commented Oct 15, 2026

Copy link
Copy Markdown
Contributor Author

works well

one thing though, admins room is still auto read which is half bug mentioned in #102954. And it is not related to /concierge path we are fixing on this PR.

Steps

  1. On mWeb (or narrow web), sign up with a new account
  2. Complete onboarding with "Submit expenses to my employer"
  3. Don't open #admins, check it in LHN

Expected: #admins is unread, it has the Concierge "Welcome to Expensify! What do you want to do first?" message

Actual: #admins shows as read. The report has lastReadTime == lastVisibleActionCreated and empty lastMessageText, older than the welcome action

RCA: CreateWorkspace is a write, so its response is held in QueuedOnyxUpdates until sequential queue drains. CompleteGuidedSetup returns with an update ID gap, GetMissingOnyxMessages applies the welcome right away, then the queue flush applies the older CreateWorkspace snapshot on top and rewinds the report summary

Desktop hides it because the app opens #admins after onboarding, which refetches the report.

So I propose we will raise a separate PR for #102954 later regarding this bug. @luacmartins does this sound good?! cc @eh2077

luacmartins
luacmartins previously approved these changes Oct 15, 2026

@pecanoro pecanoro left a comment

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.

Really small comments

Comment thread src/libs/actions/Link.ts
Comment thread src/pages/ConciergePage.tsx
Comment thread src/pages/ConciergePage.tsx
Co-authored-by: Rocio Perez-Cano <[email protected]>
mukhrr and others added 2 commits October 16, 2026 11:22
@mukhrr
mukhrr requested a review from pecanoro October 16, 2026 06:22
@mukhrr

mukhrr commented Oct 16, 2026

Copy link
Copy Markdown
Contributor Author

@pecanoro could you pls take a look at #102956 (comment) before merging this? Do you think we should include fix for #102956 here? It's related, but not regression from original PR.

@eh2077

eh2077 commented Oct 16, 2026

Copy link
Copy Markdown
Contributor

@mukhrr I think this PR already included changes to fix #102956 (comment), am I right?

@mukhrr

mukhrr commented Oct 16, 2026

Copy link
Copy Markdown
Contributor Author

Yes you are

@eh2077

eh2077 commented Oct 16, 2026

Copy link
Copy Markdown
Contributor

Chatted with @mukhrr on slack, let me try to summarize above comments, there're two relevant issues found in the first version PR.

This PR already included changes to fix it. @mukhrr commented on the issue and mentioned it isn't a regression because it still exists after reverting the first PR. They also asked #103681 (comment) if need to include fix in this PR. I think we should, or it'll block QA testing on Android App (physical device). I'll help comment the expanded scope work about payment if needed later.

@pecanoro do you agree?


This PR fixed it. During testing this issue, @mukhrr spotted a new issue about unread admin chat as mentioned in #103681 (comment), they investigated with RCA and asked to reopen the closed issue to apply a follow-up fix. While I think it's better file a new issue for it.

@luacmartins Wdyt?


Other than the above, this PR should be good to merge.

@luacmartins

Copy link
Copy Markdown
Contributor

Replied here

@pecanoro

Copy link
Copy Markdown
Contributor

@pecanoro do you agree?

Yeah, I agree, it sounds good to me

@pecanoro
pecanoro merged commit ef784ba into Expensify:main Oct 17, 2026
35 of 36 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

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

@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/pecanoro in version: 9.5.14-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

No help site update needed. This PR is a bug fix: a link opened before signing up now opens after onboarding finishes, which is what users already expect, and no article in docs/articles describes the old behavior.


view run

@jponikarchuk

Copy link
Copy Markdown

Deploy Blocker #104391 was identified to be related to this PR.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/grgia in version: 9.5.14-3 🚀

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

Bundle Size Analysis (Sentry):

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