[No QA] [ECUK In-App 3DS] Rename MFA error codes and fix unsupported device logic

[JakubKorytko]

Explanation of Change

• Renames confusing MFA reason codes (NO_ELIGIBLE_METHODS -> NO_AUTHENTICATION_METHODS_ENROLLED, UNSUPPORTED_DEVICE -> AUTHENTICATION_TYPE_NOT_SUPPORTED) for clarity.
• Fixes logic in Main.tsx by swapping the order of checks: now verifies allowed auth type first, then device capability. Adds Expo-to-generic error mapping in useNativeBiometrics.ts so failure screens match correctly.
• Makes UnsupportedDeviceFailureScreen platform-aware via native/web index files (mobile says "use web app", web says "download mobile app").

Spanish translation confirmation: https://expensify.slack.com/archives/C01GTK53T8Q/p1774443435075649

Fixed Issues

$ #85830
PROPOSAL: N/A

Tests

1. On web (Chrome/Safari), trigger an MFA flow for a scenario that only allows biometrics (e.g. if such a scenario exists, or mock allowedAuthenticationMethods to [BIOMETRICS] only)
2. Verify the failure screen shows "Unsupported device" with a message to download the Expensify mobile app

---

1. On Android/iOS native without biometrics or passcode enrolled, trigger an MFA flow (e.g. Set PIN, Authorize Transaction, or Biometrics Test)
2. Verify the failure screen shows a message to enable face/fingerprint verification or set a device passcode in system settings (not "download the app")

---

1. On Android/iOS native, trigger an MFA flow for a scenario that only allows passkeys (mock allowedAuthenticationMethods to [PASSKEYS] only)
2. Verify the failure screen shows "Unsupported device" with a message to use the Expensify web app (linking to new.expensify.com)

Offline tests

N/A

QA Steps

N/A

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

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

Web.mov

[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

[JakubKorytko]

@codex review

[codecov]

Codecov Report

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

Files with missing lines	Coverage Δ
...orAuthentication/biometrics/useNativeBiometrics.ts	100.00% <100.00%> (ø)
...ultifactorAuthentication/biometrics/usePasskeys.ts	0.00% <ø> (ø)
...en/UnsupportedDeviceFailureScreen/index.native.tsx	100.00% <100.00%> (ø)
...nts/OutcomeScreen/FailureScreen/defaultScreens.tsx	100.00% <ø> (ø)
...tication/config/scenarios/AuthorizeTransaction.tsx	38.88% <ø> (ø)
...tication/config/scenarios/DefaultUserInterface.tsx	100.00% <ø> (ø)
...rc/libs/MultifactorAuthentication/shared/VALUES.ts	100.00% <ø> (ø)
...ureScreen/UnsupportedDeviceFailureScreen/index.tsx	0.00% <0.00%> (ø)
...ponents/MultifactorAuthentication/Context/Main.tsx	13.97% <0.00%> (ø)
... and 33 files with indirect coverage changes

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a7896b1303

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

[melvin-bot]

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

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

[DylanDylann]

@dmkt9 @m-natarajan Please ignore this PR. I will take over this

[trjExpensify]

ECUK project PR 👍

[DylanDylann]

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
  • MacOS: Desktop
• 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 there are no new alerts related to the canBeMissing param for useOnyx
• 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

On Android/iOS native without biometrics or passcode enrolled, trigger an MFA flow (e.g. Set PIN, Authorize Transaction, or Biometrics Test)

Screen.Recording.2026-03-26.at.22.14.55.mov

On Android/iOS native, trigger an MFA flow for a scenario that only allows passkeys (mock allowedAuthenticationMethods to [PASSKEYS] only)

Screen.Recording.2026-03-26.at.22.14.05.mov

iOS: HybridApp

On Android/iOS native without biometrics or passcode enrolled, trigger an MFA flow (e.g. Set PIN, Authorize Transaction, or Biometrics Test)

Screen.Recording.2026-03-26.at.22.15.34.mov

On Android/iOS native, trigger an MFA flow for a scenario that only allows passkeys (mock allowedAuthenticationMethods to [PASSKEYS] only)

Screen.Recording.2026-03-26.at.22.10.27.mov

MacOS: Chrome / Safari

On web (Chrome/Safari), trigger an MFA flow for a scenario that only allows biometrics (e.g. if such a scenario exists, or mock allowedAuthenticationMethods to [BIOMETRICS] only)

Screen.Recording.2026-03-26.at.22.08.27.mov

[DylanDylann]

@JakubKorytko I see an error on IOS when trying the biometric scenario (Note: need to remove biometric from allowedAuthenticationMethods)

[JakubKorytko]

@DylanDylann ah it's because of the circular import. Reverted this change - works good for me now, please re-test.

[DylanDylann]

The rest looks fine to me

[melvin-bot]

We did not find an internal engineer to review this PR, trying to assign a random engineer to #85830 as well as to this PR... Please reach out for help on Slack if no one gets assigned!

[DylanDylann]

cc @rafecolton @chuckdries

[chuckdries]

LGTM!

[chuckdries]

I will say, I know this wasn't introduced in this PR, and it seems like it's not particularly solvable (RN's Linking.openSettings doesn't take any parameters), but I wish the "system settings" link actually took the user somewhere useful on android. This is definitely an edge case (who doesn't have a screen lock set in 2026?!) but if you do indeed not have a screen lock set, there's actually no way to navigate from the page the button takes you to, to the page you need to use to set up a screen lock

android hybridapp

system.settings.link.mp4

Honestly, maybe we just don't link it at all on Android as a follow-up

[chuckdries]

Oh, I just noticed, @JakubKorytko QA is not going to be able to execute the test steps because they cannot mock code values. Can you write QA steps that they'll actually be able to perform? Thanks

[github-actions]

🚧 @chuckdries 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 #86317.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-7ac7a48-5568f7f-9c6de2787f7429293e46dbb2eb326f9e09975fc6/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-7ac7a48-5568f7f-ee637a1832bf00fa815613c41f8462787d852b08/index.html

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

---

👀 View the workflow run that generated this build 👀

[OSBotify]

✋ 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]

🚀 Deployed to staging by https://github.com/chuckdries in version: 9.3.50-0 🚀

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

Bundle Size Analysis (Sentry):

• Android
• iOS

[MelvinBot]

🤖 Help Site Review — No Changes Required

I reviewed all files under docs/articles/ against the changes in this PR, applying the guidelines from HELPSITE_NAMING_CONVENTIONS.md, HELP_AUTHORING_GUIDELINES.md, and TEMPLATE.md.

Findings:

This PR modifies internal MFA error codes, reorders device-check logic, and makes the UnsupportedDeviceFailureScreen platform-aware (mobile → "use web app", web → "download mobile app"). These are all changes to the in-app biometrics/passkeys MFA flow used for ECUK transaction authorization.

The existing help site articles that are closest in topic are:

• new-expensify/expensify-card/Expensify-Card-3D-Secure-Verification.md
• expensify-classic/expensify-card/Expensify-Card-3D-Secure-Verification.md

However, these articles exclusively describe SMS OTP-based 3D Secure verification (the Verified by Visa flow). They do not reference:

• Biometrics or passkey-based authentication
• The in-app MFA flow or its error screens
• "Unsupported device" error messages
• Any of the internal reason codes being renamed

No other article under docs/articles/ mentions biometrics, passkeys, device verification, or the MultifactorAuthentication component.

Conclusion: No help site changes are required for this PR. The modified error codes and platform-specific error screens are purely internal to the in-app MFA flow, which is not yet documented in any help site article.

[OSBotify]

🚀 Deployed to production by https://github.com/jasperhuangg in version: 9.3.50-8 🚀

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