feat: re-add the new onboarding for private domains

[allroundexperts]

Details

$ #48189

Fixed Issues

$ #48189
PROPOSAL: #48189 (comment)

Tests

** Test Case 1 **

1. Login using an email that is private (Make sure that another user exists on the same private domain and has several workspaces created)
2. Verify that an onboarding modal appears, asking to input your name.
3. Enter your name, and verify that after clicking next, you're prompted to enter the OTP.
4. Enter the OTP, and verify that after clicking next, you're shown a list of workspaces to join.
5. Join any workspace, and verify that you see the new workspace in the LHN.

** Test Case 2 **

1. Make sure that another user exists on the same private domain and has a workspace create that has pre-approval of new members turned off. This needs to be done through Old dot, by going over to the workspace settings, and navigating to the members section.
2. Login using a new email that is on the same private domain as 1.
3. Verify that an onboarding modal appears, asking to input your name.
4. Enter your name, and verify that after clicking next, you're prompted to enter the OTP.
5. Enter the OTP, and verify that after clicking next, you're shown the workspace created in step 1 and it has a button that reads Ask to join.
6. Click on the button.
7. As a user in step 1, go to the #admins chat, and make sure that you see a message asking that the user in step 2 intends to join the workspace.
8. Accept the request.
9. Sign in as user in step 2, and verify that the new workspace shows in the LHN.

• Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

Same as test steps

• 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
  • MacOS: Desktop
• 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 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 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

Unable to build android

Android: mWeb Chrome

Screen.Recording.2025-02-07.at.1.15.46.AM.mov

iOS: Native

Screen.Recording.2025-02-07.at.1.12.18.AM.mov

iOS: mWeb Safari

Screen.Recording.2025-02-07.at.1.10.09.AM.mov

MacOS: Chrome / Safari

Screen.Recording.2025-02-07.at.1.04.27.AM.mov

MacOS: Desktop

Screen.Recording.2025-02-07.at.1.07.35.AM.mov

[melvin-bot]

@parasharrajat 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]

[parasharrajat]

@allroundexperts Merge main and fix namespaces lint issue,

[parasharrajat]

Screenshots

🔲 iOS / native

10.02.2025_11.58.13_REC.mp4

🔲 iOS / Safari

🔲 MacOS / Desktop

🔲 MacOS / Chrome

10.02.2025_11.31.37_REC.mp4

10.02.2025_11.35.54_REC.mp4

10.02.2025_11.46.41_REC.mp4

🔲 Android / Chrome

🔲 Android / native

[parasharrajat]

BUG: App crash on entering wrong verification code.

10.02.2025_13.32.44_REC.mp4

[parasharrajat]

Bugs

[parasharrajat]

BUG: Continuing onboarding from a different platform, does not show any workplace on Join workspaces list.

Note; This was reported in last PR also. #51681 (comment)

[parasharrajat]

BUG: User is showing later steps before personal details step is shown.

Steps:

1. Login with a user and complete a few steps in flow.
2. close the app or page.
3. Go to that page again.

10.02.2025_13.39.13_REC.mp4

[danielrvidal]

Awesome, thank you for the quick work on this one. Hopefully we'll get it out soon!

[allroundexperts]

BUG: Continuing onboarding from a different platform, does not show any workplace on Join workspaces list.

Note; This was reported in last PR also. #51681 (comment)

This is happening because when you login via normal flow ie SIGN_IN_USER command, pusher updates hasAccessibleDomainPolicies parameter of the user object, but does not send back the JOINABLE_POLICIES key. We need to fix this in the backend such that whenever a login happens, the pusher should send the policies accessible as well.

[allroundexperts]

BUG: App crash on entering wrong verification code.

This is happening again due to a case we missed on the backend. When we use VALIDATE_USER_AND_GET_ACCESSIBLE_POLICIES command, if the validation code is incorrect, the pusher sends back the error as:

{
    "onyxMethod": "merge",
    "key": "onboardingErrorMessage",
    "value": {
        "errors": {
            "1739293208291145": "Invalid code"
        }
    }
}

onboardingErrorMessage key does not indicate what step the validation failed at, and hence it does not make sense to use it. Instead, can the error be sent back to the VALIDATE_USER_AND_GET_ACCESSIBLE_POLICIES key? That will allow for more easier validation.

[allroundexperts]

BUG: User is showing later steps before personal details step is shown.

Steps:

1. Login with a user and complete a few steps in flow.
2. close the app or page.
3. Go to that page again.

10.02.2025_13.39.13_REC.mp4

I am unable to reproduce this. Can you please post more clear reproduction steps? Also, if possible, can you give it a shot on incognito mode?