Skip to content

[HybridApp] Implement POC of NewDot SignIn on HybridApp#51257

Merged
Julesssss merged 148 commits intoExpensify:mainfrom
software-mansion-labs:make-new-dot-signin-default-for-hybridapp
Jun 17, 2025
Merged

[HybridApp] Implement POC of NewDot SignIn on HybridApp#51257
Julesssss merged 148 commits intoExpensify:mainfrom
software-mansion-labs:make-new-dot-signin-default-for-hybridapp

Conversation

@mateuuszzzzz
Copy link
Contributor

@mateuuszzzzz mateuuszzzzz commented Oct 22, 2024

Details

This PR refactors existing functionalities on mobile devices, but it's possible it's caused a regression on web or desktop, hence testing other platforms is also necessary.

Fixed Issues

$ #49844
PROPOSAL:

MOBILE-EXPENSIFY: https://github.com/Expensify/Mobile-Expensify/pull/13284

Tests

Base information to every flow:
The flow is based on NVP tryNewDot value, we have two possible scenarios to test:

  • tryNewDot is properly set
  1. Log out from ND
  2. Log in using any flows bellow
  3. Verify that you end up in ND (dismissed == false)
  4. Move to OD using Switch to Expensify Classic button
  5. Log out from OD
  6. Verify that you end up in ND sign in page and the transition is seamless (no bootsplash and no white screen)
  7. Log in with the same account
  8. Verify you end up in OD (dismissed == true)
  • tryNewDot is undefined. This state can be achieved by having old classic account or manually setting await NVP.set("tryNewDot", undefined); in Expenisfy classic on web.
  1. Open app
  2. Try to log in using preset account described above and any flow
  3. Verify that you user is moved straight to OD and Try New Expensify button is no visible
  4. Log out
  5. Verify that you end up in ND sign in page and the transition is seamless (no bootsplash and no white screen)

Main flow:

  1. Provide email
  2. Enter magic code

Main flow new Account:

  1. Provide new email
  2. Press Join
  3. Verify that onboarding starts
  4. Verify that onboarding cannot be dismissed by pressing hardware back button.

SAML Magic code

  1. Provide email that uses SAML
  2. Press Use magic code
  3. Enter magic code

SAML single sign on

  1. Provide email that uses SAML
  2. Press single sign-on
  3. Login via SAML
  4. Verify that app opens properly and not inside WebView

Google sign-in Apple sign-in:
Both flows have different implementation depending on OS and need to be tested exhaustively
Verify that no errors or Growls appear.

2FA:

  1. Log in to ND.
  2. Add 2FA to the account
  3. Sign out
  4. Login again using the authenticator app

Travel, OD <-> ND switch etc
Verify that:

  1. Travel from OD work according to [HybridApp] Allow classic experience users to use NewDot travel page #49602 (comment)
  2. After sign-in ND share extension works properly
  3. That changing copilot in OD/ND changes copilot in other app.
  4. When changing copilot in ND no navigation happens
  5. User with tryNewDot can transition between OD and ND.
  6. Deeplinks navigate to appropriate app depending on the link
  7. Verify that shortcuts work and navigate to app depending on where user is logged.

Offline tests

QA Steps

Same as tests

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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
    • 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 verified the translation was requested/reviewed 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.js 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.
  • 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
MacOS: Desktop

war-in and others added 25 commits October 31, 2024 12:03
# Conflicts:
#	src/libs/actions/Session/index.ts
* Implement ND bootsplash logic

* Rename param

* Adress review
# Conflicts:
#	src/ONYXKEYS.ts
#	src/libs/actions/Session/index.ts
#	src/types/modules/react-native.d.ts
* Add hybridAppSettings AppProp

* Unify how we pass data on both platforms

* fix after merge

* fix comments

---------

Co-authored-by: war-in <war-in@users.noreply.github.com>
* wip

* block switching when error returned

* make goBack work correctly

* validate code form and SignIn button works (but require further investigation)

* show error when unable to switch to OD

* adjust new sign-up flow

* add comment

---------

Co-authored-by: war-in <war-in@users.noreply.github.com>
@mateuuszzzzz
Copy link
Contributor Author

mateuuszzzzz commented Jun 17, 2025

FYI: It looks like translations are loaded with delay (components mount first and then we get valid translations). I'm working on a solution to speed up this process and guarantee that UI renders when at least one language is loaded.

@mateuuszzzzz
Copy link
Contributor Author

I managed to fix this issue.

fixed.locale.mov

@tgolen
Copy link
Contributor

tgolen commented Jun 17, 2025

Hi all, thanks for considering to remove the Onyx.connect(). I know it is a big ask to remove it, and technically it hasn't been deprecated yet. However, it's got to be removed at some point, so it would be nice to remove it before even deploying it. I won't press too hard either way since I'm not the one that has to do the work.

@Julesssss
Copy link
Contributor

I know it is a big ask to remove it, and technically it hasn't been deprecated yet. However, it's got to be removed at some point, so it would be nice to remove it before even deploying it. I won't press too hard either way since I'm not the one that has to do the work.

@tgolen I'm going to create a follow up issue for this. This refactor is 6+ months in the works with a F1 deadline for next week. On top of this the lazy load PR introduced issues here preventing us from shipping as we intended to this week.

@tgolen
Copy link
Contributor

tgolen commented Jun 17, 2025 via email

@Julesssss
Copy link
Contributor

We have a solution to the translation issue, merging and we'll resolve any conflicts on the fix PR.

@Julesssss Julesssss merged commit d637046 into Expensify:main Jun 17, 2025
27 checks passed
@OSBotify
Copy link
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.

@github-actions
Copy link
Contributor

🚀 Deployed to staging by https://github.com/Julesssss in version: 9.1.69-0 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 failure ❌

@Julesssss
Copy link
Contributor

For anyone noticing a regression related to these changes, we need to avoid a revert due to the scale of this and the accompanying Mobile-Expensify PR.

@289Adam289, @war-in @mateuuszzzzz and myself (back Friday) will be able to help you resolve these issues. For any non-blockers, please add them here.

@github-actions
Copy link
Contributor

🚀 Deployed to staging by https://github.com/Julesssss in version: 9.1.69-0 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 failure ❌

@github-actions
Copy link
Contributor

🚀 Deployed to staging by https://github.com/Julesssss in version: 9.1.69-0 🚀

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

@github-actions
Copy link
Contributor

🚀 Deployed to production by https://github.com/lakchote in version: 9.1.69-3 🚀

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

@Expensify Expensify deleted a comment from github-actions bot Jun 27, 2025
@Expensify Expensify deleted a comment from github-actions bot Jun 27, 2025
@Expensify Expensify deleted a comment from github-actions bot Jun 27, 2025
@Expensify Expensify deleted a comment from github-actions bot Jun 27, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Jun 27, 2025

@Julesssss Julesssss mentioned this pull request Jul 30, 2025
49 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.