Bug fix: first biometric auth after log out/in sees unnecessary soft prompt

[rafecolton]

Explanation of Change

Fixes a bug where a user registers a passkey or mobile native biometrics, logs out, logs in, and sees a soft prompt before authenticating, as opposed to the authorization screen.

This fix also ensures that if the app is entirely deleted from a device and reinstalled, that we DO show the soft prompt again. That is still needed because iOS will show the system prompt in that case.

Fixed Issues

$ #86284
PROPOSAL: N/A

Tests

Web

1. Navigate to the troulbeshoot page in a fresh incognito on web
2. Tap Test and register a passkey. You should see the "soft prompt" first (it's a page that says "Enable quick, secure..." and has a green button).
3. Log out and back in to the same account in the same browser session
4. Navigate to troubleshoot and confirm you are still registered
5. Tap test. You should see the Now, let's authenticate you... screen with the spinner right away, and you should not have to click any green button to get the browser passkey prompt.

iOS

1. Make sure you start with a fresh install. This doesn't just mean an update. It means delete and reinstall the app.
2. Log in with a fresh account.
3. Navigate to Troubleshoot and register for biometrics.
   1. You should see the soft prompt first
   2. You may see the system prompt (system popup that asks you if you want to allow Face ID for the app). Make sure to allow it if you do see it.
   3. You should be prompted to authenticate with Face ID twice, and the screen will change in between
4. Log out and back in.
5. Go to Troubleshoot again, confirm you're still registered, and tap Test. You should go to authentication right away and not see the soft or the system prompt.
6. Delete and reinstall the app, then log in with the same account as before.
7. Log in, go to troubleshoot, confirm you're still registered, and tap Test
   1. You should see the soft prompt
   2. You may see the system prompt. Allow it if you do.
   3. You should be prompted for Face ID once.

• Verify that no errors appear in the JS console

Offline tests

N/A, online only

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

iOS: Native

Screen.Recording.2026-03-24.at.5.16.49.PM.mov

MacOS: Chrome / Safari

Screen.Recording.2026-03-24.at.4.59.47.PM.mov

[codecov]

Codecov Report

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

Files with missing lines	Coverage Δ
src/ONYXKEYS.ts	100.00% <ø> (ø)
...ponents/MultifactorAuthentication/Context/Main.tsx	13.97% <100.00%> (+1.41%)	⬆️
src/libs/actions/App.ts	46.94% <ø> (ø)
src/libs/actions/Delegate.ts	31.63% <ø> (ø)
src/libs/actions/Session/index.ts	43.63% <ø> (ø)
src/libs/actions/SignInRedirect.ts	78.72% <100.00%> (+0.46%)	⬆️
src/pages/MultifactorAuthentication/PromptPage.tsx	0.00% <ø> (ø)
...tifactorAuthentication/Context/usePromptContent.ts	0.00% <0.00%> (ø)
...rc/libs/actions/MultifactorAuthentication/index.ts	16.19% <50.00%> (+1.62%)	⬆️
... and 11 files with indirect coverage changes

[melvin-bot]

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

[rafecolton]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 676ccffb1d

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

[chatgpt-codex-connector]

Migrate legacy soft-prompt state to account-scoped key

This read now only checks deviceBiometrics_${accountID}, but the previous value was stored under the legacy non-collection key, so existing users who already accepted the soft prompt will be treated as first-time until they re-approve. In practice, the first MFA authorization after this upgrade can show an unnecessary soft prompt even without reinstall/logout. Add a migration or fallback read from the legacy key during the transition.

Useful? React with 👍 / 👎.

[rafecolton]

It is known and acceptable - this is not a commonly used feature, as the main use for it is behind a beta, and the UX cost of re-registration is low. I don't think it's worth the complexity to add a migration.