Fix/add descriptive sso error message

[mnshrm]

Explanation of Change

PR adds logic to render specific error message for SSO work email error, when a work email is entered during onboarding with single sign on enabled.

Fixed Issues

$ #91566
PROPOSAL: $ #91566 (comment)

Tests

PRECONDITION: Create an account with a work email with single sign on enabled in order to simulate SSO/SAML error message. (for example applausetester+vq+1104@applause.expensifail.com)

1. Scenario : SSO/SAML error is displayed when user attempts to enter a work email already associated to a account with SSO enabled
   1. Navigate to new expensify
   2. Enter a new email id, and click on continue button.
   3. Click on join button
   4. Wait for new onboarding flow popup.
   5. On 'what's your work email' popup, enter a work email already associated with an account with SSO enabled.
   6. Click on add work email button.
   7. Error should be displayed with message 'This login is an existing account with SSO/SAML enabled.'
   8. user attempts to correct mistake, by modifying work email input.
   9. Error should be removed and not be displayed as soon as input value changes.

• Verify that no errors appear in the JS console

Offline tests

PRE-REQUISITE: A account with work email and SSO enabled.

1. Scenario: Verify offline error for 'what's your work email' form
   1. Navigate to new expensify
   2. Enter a new email id, and click on continue button.
   3. Click on join button
   4. Wait for new onboarding flow popup.
   5. On 'what's your work email' popup, enter a work email already associated with an account with SSO enabled.
   6. Go offline (by using airplane mode, or using dev tools or any other preferred method)
   7. Click on add work email button.
   8. Error 'We couldn’t add your work email as you appear to be offline' is displayed

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 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
  • 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 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.
• 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

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

[melvin-bot]

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

1. Look at the code and make sure there are no malicious changes.
2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

[codecov]

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/CONST/index.ts	93.84% <ø> (+0.04%)	⬆️
src/libs/actions/Session/index.ts	42.37% <100.00%> (-0.37%)	⬇️
...es/OnboardingWorkEmail/BaseOnboardingWorkEmail.tsx	85.36% <100.00%> (+2.64%)	⬆️
... and 309 files with indirect coverage changes

[melvin-bot]

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

[QichenZhu]

@mnshrm please use the exact same text copy in this comment and update translations. Thanks!

[mnshrm]

@QichenZhu, Thanks for the review, translations have been updated as per the the comment

[QichenZhu]

@mnshrm please remove any redundant test steps as they will confuse testers. Thanks!

[QichenZhu]

@mnshrm also,

1. Your screenshots don't include the third scenario. Please reconsider whether it is necessary and add screenshots if so.

2. QA test steps are empty.

[QichenZhu]

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
  https://expensify.slack.com/archives/C049HHMV9SM/p1778663561704459
• I verified proper code patterns were followed (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
  • 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 verified that this PR follows the guidelines as stated in the Review Guidelines
• 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)
• 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
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • 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
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • 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 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.
• 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-06-09.at.2.13.17.PM.mov

Android: mWeb Chrome

Screen.Recording.2026-06-09.at.2.15.50.PM.mov

iOS: HybridApp

Simulator.Screen.Recording.-.iPhone.17.-.2026-06-09.at.14.21.53.mov

iOS: mWeb Safari

Simulator.Screen.Recording.-.iPhone.17.-.2026-06-09.at.14.17.34.mov

MacOS: Chrome / Safari

Screen.Recording.2026-06-09.at.1.28.21.PM.mov

Screen.Recording.2026-06-09.at.1.37.33.PM.mov

[QichenZhu]

We need to increase or maintain test coverage. You can refer to tests/ui/WorkEmailOnboarding.tsx. Let me know if you need help.

[mnshrm]

@QichenZhu, Thanks for the detailed review

1. Removed redundant tests and steps from tests section and also filled QA tests as well.
2. 3rd scenario is out of scope of this PR, but is a valid 'happy path' test case which requires real work email id unfortunately I don't have a work email id to test it out, I can test till OTP page.
3. Added automated test cases to check for 2FA and SSO error messages if appropriate response is received.

[QichenZhu]

LGTM.

[github-actions]

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

[github-actions]

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #92713.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-3ee7c99eba9-5dd32c1-def0d445f13b7769001e0b2c8f2c7eb67a4f8d1a/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-3ee7c99-5dd32c1-1891acd2c546c832bee7cea6312f8209360d2e5a/index.html

Web 🕸️
https://92713.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀

[OSBotify]

🚀 Deployed to staging by https://github.com/arosiclair in version: 9.4.5-0 🚀

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

Bundle Size Analysis (Sentry):

• Android
• iOS

[MelvinBot]

Help site review: no docs changes required

I reviewed the changes in this PR against the help site articles under App/docs/articles and no help site updates are required.

What this PR changes

It adds a single localized inline error message (onboarding.singleSignOnError → "This login is an existing account with SSO/SAML enabled.") that surfaces during the What's your work email? onboarding step when the entered work email already belongs to an account with SSO/SAML enabled. The change is the error string (added to all src/languages/* locales), the matching CONST server-error mapping, and the offline-feedback gating in BaseOnboardingWorkEmail.

Why no docs update is needed

• This is an inline UI validation/error message for a narrow onboarding edge case, not a new feature, setting, tab, or workflow.
• It exactly mirrors two pre-existing inline errors in the same flow — workEmail2FAError and mergeBlockScreen.workAccountClosedSubtitle — neither of which is documented in any help article. There is no help content that enumerates onboarding work-email error states.
• I searched docs/articles for the onboarding work-email step and its errors (work email, SSO, SAML, 2FA error, onboarding). The closest articles — Login-Troubleshooting, Set-Up-SAML-SSO, and Join-your-company's-workspace — cover logging in with SAML SSO and setting up SSO for a domain, not the onboarding work-email entry step. None describe the inline error behavior this PR touches, so there is nothing to add or correct.

Because no documented behavior is affected, I did not create a draft docs PR.

@mnshrm, please confirm you agree that no help site changes are needed here. If you believe a new or updated article is warranted (e.g. a troubleshooting entry for the onboarding work-email step), let me know and I'll draft one.

[OSBotify]

🚀 Deployed to production by https://github.com/Julesssss in version: 9.4.5-6 🚀

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