[Due for payment 2026-06-24] [$250] iOS - Biometrics - The Test Tool menu does not close after tapping Test

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.3.98.0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-37778/folder/13176687/96645709/1459453133?sort=%2Bidentifier&p=2
Email or phone of affected tester (no customers): n/a
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: iPhone 13 iOS 26.5
App Component: Other

Action Performed:

1. Open the app
2. Trigger Test Tool: Tap the screen with 4 fingers simultaneously to bring up the hidden Test Tool menu
3. Tap Test Locate and tap the Biometrics row

Expected Result:

After tapping Test, the Test Tool menu should close and the Let's verify it's you page appears

Actual Result:

The Test Tool menu does not close after tapping Test

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome Safari

Screenshots/Videos

Bug7170652_1780503236926.ScreenRecording_06-03-2026_11-10-13_1.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7170652

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022062221311506291401
• Upwork Job ID: 2062221311506291401
• Last Price Increase: 2026-06-03

Issue Owner

Current Issue Owner: @mallenexpensify

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/098e9acb632264d61fc6a31d668c5982ae946db9e18ed9c06ea4b0d85f5ef578

[MelvinBot]

Proposal

What is the root cause of that problem?

The Test button in the Biometrics Test Tool row only kicks off the MFA scenario — it never dismisses the Test Tools modal. In BiometricsTestToolRow.tsx:36 the onPress is just:

onPress={() => executeScenario(CONST.MULTIFACTOR_AUTHENTICATION.SCENARIO.BIOMETRICS_TEST)}

executeScenario sets the MFA state open, which renders the "Let's verify it's you" overlay. But on iOS that overlay ends up behind the still-open Test Tools menu, so it looks like nothing happened.

This is a z-order problem specific to native:

• The Test Tools modal is presented with presentation: 'transparentModal' (useRootNavigatorScreenOptions.ts:53-54, wired at AuthScreens.tsx:361-378). On iOS this is a real native modal view controller that sits above the React root.
• The MFA overlay is just an absolute-fill React View rendered as a sibling after RootStack.Navigator (AuthScreens.tsx:383; the View is at MultifactorAuthenticationModalNavigator.tsx:138-142).

On web both are DOM siblings and the later one (MFA) paints on top, so the menu appears to "close". On iOS the native transparent modal stays on top of the MFA overlay → the menu never closes and the verification page is hidden behind it.

What changes do you think we should make in order to solve the problem?

Dismiss the Test Tools modal in the same handler that starts the scenario, so the native modal is gone before the MFA overlay needs to be visible. In BiometricsTestToolRow.tsx:36, have the Test button close the Test Tools modal (e.g. via Navigation.goBack(), mirroring how toggleTestToolsModal already dismisses it in TestTool.ts:31-37) and then call executeScenario(...).

This matches the expected result exactly: the Test Tool menu closes and the "Let's verify it's you" page appears on top.

What alternative solutions did you explore? (Optional)

Notes & things considered

• Why only iOS: the report only ticks iOS: App. The mechanism (native transparentModal above the React-root MFA overlay) would also affect Android App; web is unaffected because the overlay is a later DOM sibling. Worth a quick Android check during QA.
• Why other Test Tool rows don't show this: the other actions (Invalidate, Destroy, etc.) don't open a new full-screen page, so they don't need the menu to close. Biometrics is the only row expected to navigate to a separate verification page.
• I did not verify this on a device/simulator — the App web tester can't reproduce an iOS-only native-modal stacking issue, so the iOS behavior here is reasoned from the navigation config rather than observed. Confidence on the root cause (menu never dismissed) is high; the exact native stacking is the explanation for the iOS-specific symptom.
• No other open issues matched this symptom.

---

Next Steps for Contributor+ team:
To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/92558) to create a draft PR.
To refine: @MelvinBot <your feedback>
To reject: Explain why you are rejecting Melvin's proposal.

[MobileMage]

Proposal

Please re-state the problem that we are trying to solve in this issue.

On iOS, opening the hidden Test Tool menu (4-finger tap) and pressing the Test button next to the Biometrics row launches the MFA "Let's verify it's you" overlay, but the Test Tool menu stays mounted underneath. The expected behavior is for the Test Tool menu to dismiss so only the biometric verification screen is visible.

What is the root cause of that problem?

The Test Tool menu and the MFA overlay are two independent UI surfaces. The Test Tool menu lives inside the root navigator as a screen at NAVIGATORS.TEST_TOOLS_MODAL_NAVIGATOR (see AuthScreens.tsx line 361-380), so dismissing it requires popping that route via Navigation.goBack(). The MFA overlay, by contrast, is rendered as a sibling of RootStack.Navigator and uses a separate NavigationIndependentTree whose visibility is driven purely by the isModalOpen Onyx-derived state in MultifactorAuthenticationStateContext:

App/src/libs/Navigation/AppNavigator/AuthScreens.tsx

Lines 361 to 383 in 8020a93

	<RootStack.Screen
	name={NAVIGATORS.TEST_TOOLS_MODAL_NAVIGATOR}
	options={{
	...rootNavigatorScreenOptions.basicModalNavigator,
	native: {
	contentStyle: {
	...StyleUtils.getBackgroundColorWithOpacityStyle(theme.overlay, 0.72),
	},
	animation: InternalPlatformAnimations.FADE,
	},
	web: {
	cardStyle: {
	...StyleUtils.getBackgroundColorWithOpacityStyle(theme.overlay, 0.72),
	},
	animation: InternalPlatformAnimations.FADE,
	},
	}}
	component={TestToolsModalNavigator}
	listeners={modalScreenListeners}
	/>
	</RootStack.Navigator>
	<RequireTwoFactorAuthenticationOverlay />
	<MultifactorAuthenticationModalNavigator />

When the user taps Test in BiometricsTestToolRow, the onPress handler calls only executeScenario(CONST.MULTIFACTOR_AUTHENTICATION.SCENARIO.BIOMETRICS_TEST). That dispatches an INIT action to the MFA reducer, which sets isModalOpen: true (see stateReducer.ts line 87) and causes MultifactorAuthenticationModalNavigator to mount its absoluteFill overlay and slide the prompt page in. Because the MFA navigator is a sibling overlay — not a child of the root stack — mounting it does not pop the Test Tools route. The Test Tool menu therefore remains active in the root stack beneath the MFA overlay, and you can still see it (and re-encounter it after the MFA flow ends).

// BiometricsTestToolRow.tsx (line 36) — the Test button only triggers MFA, never dismisses the host menu
onPress={() => executeScenario(CONST.MULTIFACTOR_AUTHENTICATION.SCENARIO.BIOMETRICS_TEST)}

App/src/components/BiometricsTestToolRow.tsx

Lines 32 to 37 in 8020a93

	<Button
	small
	isDisabled={isOffline}
	text={translate('multifactorAuthentication.biometricsTest.test')}
	onPress={() => executeScenario(CONST.MULTIFACTOR_AUTHENTICATION.SCENARIO.BIOMETRICS_TEST)}
	/>

This is in contrast to the existing host-dismissal entry points for the Test Tool menu — useDebugShortcut, the outer-click handler in TestToolsModalNavigator, the Escape shortcut, and the 4-finger gesture in ScreenWrapperContainer — which all call toggleTestToolsModal() to navigate back from the ROUTES.TEST_TOOLS_MODAL route. No equivalent dismissal happens when the Test button is pressed, which is why the menu lingers on iOS (and on every other platform where this row is rendered, but the issue happens to be filed against iOS).

What changes do you think we should make in order to solve the problem?

Dismiss the host Test Tool menu inside the Test button's onPress by calling toggleTestToolsModal() immediately before executeScenario(...) in src/components/BiometricsTestToolRow.tsx. toggleTestToolsModal already detects the current route and pops it via Navigation.goBack() (see src/libs/actions/TestTool.ts lines 31-37), and it is internally throttled with leading: true, trailing: false so a double-tap will not reopen it. The MFA overlay is mounted by a separate isModalOpen-driven state machine in a sibling subtree, so popping the Test Tools route does not unmount or cancel the in-flight MFA flow — both transitions run in parallel and the user is left looking at the prompt page only, which is the expected outcome.

// src/components/BiometricsTestToolRow.tsx
import toggleTestToolsModal from '@userActions/TestTool';

// ...
onPress={() => {
    toggleTestToolsModal();
    executeScenario(CONST.MULTIFACTOR_AUTHENTICATION.SCENARIO.BIOMETRICS_TEST);
}}

The fix is localized to a single call site and matches the convention already used everywhere else the Test Tool menu is dismissed (route-level Navigation.goBack via toggleTestToolsModal). It also leaves the existing Revoke button — which intentionally stays in the menu while loading — untouched.

What alternative solutions did you explore? (Optional)

We considered dismissing the Test Tools route from inside executeScenario whenever the active route is SCREENS.TEST_TOOLS_MODAL.ROOT, but that couples generic MFA orchestration to a specific developer UI and would surprise any future caller that legitimately wants the host modal to stay (e.g. a future inline biometrics widget). We also considered adding a Navigation.dismissModal() inside the MFA navigator's mount effect, but that would compete with every other host (RHP, deep links, 3DS challenge entry) and would risk dismissing legitimate parent modals like the card details RHP that wraps RevealCardDetails. Keeping the fix at the BiometricsTestToolRow call site is the smallest, safest change.

[aswin-s]

Proposal

Please re-state the problem that we are trying to solve in this issue.

On iOS, when a user opens the hidden Test Tool menu (4-finger tap) and taps the "Test" button on the Biometrics row, the Test Tool menu does not close. The expected behavior is that the Test Tool menu closes and the "Let's verify it's you" MFA prompt is presented on top. Instead, the TestToolsModal remains open, obscuring or blocking the MFA flow.

What is the root cause of that problem?

In src/components/BiometricsTestToolRow.tsx:36, the Test button's onPress only invokes executeScenario(CONST.MULTIFACTOR_AUTHENTICATION.SCENARIO.BIOMETRICS_TEST). It never calls toggleTestToolsModal() to dismiss the TestToolsModal that hosts TestToolMenu (see src/libs/actions/TestTool.ts:60 — toggleTestToolsModal is the only mechanism that closes the modal, used by the 4-finger gesture in src/components/ScreenWrapper/ScreenWrapperContainer.tsx:173 and the ESC key in src/libs/Navigation/AppNavigator/Navigators/TestToolsModalNavigator.tsx:40). Because executeScenario triggers MFA navigation (mfaNavigate in MultifactorAuthenticationMainContext.tsx) while the TestToolsModal is still mounted, the Test Tool menu remains visible over the biometrics prompt.

What changes do you think we should make in order to solve the problem?

1. In src/components/BiometricsTestToolRow.tsx, import toggleTestToolsModal from @userActions/TestTool.
2. Update the Test Button's onPress at src/components/BiometricsTestToolRow.tsx:36 to first call toggleTestToolsModal() and then executeScenario(CONST.MULTIFACTOR_AUTHENTICATION.SCENARIO.BIOMETRICS_TEST) so the TestTools modal is dismissed before the MFA flow opens.
3. Apply the same dismissal to the Revoke Button onPress at src/components/BiometricsTestToolRow.tsx:45 (Revoke also navigates to a MultifactorAuthentication page — src/pages/MultifactorAuthentication/RevokePage.tsx), to keep the two buttons consistent.
4. No iOS-specific twin file exists for BiometricsTestToolRow — the single file applies to all platforms, so no platform fork is needed.
5. Update tests/ui/TestToolMenuBiometricsTest.tsx to assert that pressing Test calls toggleTestToolsModal before executeScenario.

What alternative solutions did you explore? (Optional)

Closing the TestToolsModal from inside executeScenario itself was considered but rejected: executeScenario is invoked from non-test-tool contexts (RevealPIN, AuthorizeTransaction, etc.) where no Test Tool modal is open, so dismissing it there would be incorrect coupling. The dismissal belongs at the call site that owns the modal.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @jjcoffee (External)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022062221311506291401

[yusufdeveloper2903]

🚫 Duplicated proposal withdrawn by 🤖 ProposalPolice.

[moxw]

Proposal

What is the root cause of that problem?

The Biometrics Test button in src/components/TestToolMenu.tsx directly calls Navigation.navigate(ROUTES.MULTIFACTOR_AUTHENTICATION_BIOMETRICS_TEST) while the Test Tools modal navigator is still the active route.

NAVIGATORS.TEST_TOOLS_MODAL_NAVIGATOR is a separate modal route, and the biometrics test flow is another modal/RHP flow. Since the Test Tools route is never dismissed before starting the MFA biometrics route, iOS can keep the Test Tools modal mounted/visible above the “Let’s verify it’s you” page.

What changes do you think we should make in order to solve the problem?

Close the Test Tools modal before navigating to the biometrics test route.

Concretely:

1. Add/reuse a Test Tools close helper in src/libs/actions/TestTool.ts that follows the same close behavior as the current toggle path:

   • read the existing backTo param with getBackToParam()
   • call Navigation.goBack(backTo) when present, otherwise Navigation.goBack()
   • support an optional afterTransition callback

2. Update the Biometrics Test button in src/components/TestToolMenu.tsx so it does:

   • close the Test Tools modal first
   • in the close transition callback, call Navigation.navigate(ROUTES.MULTIFACTOR_AUTHENTICATION_BIOMETRICS_TEST)

This keeps the existing singleExecution / useWaitForNavigation protection for rapid taps, but changes the navigation order so the Test Tools modal is removed before the MFA flow is opened.

3. Add coverage in tests/ui/TestToolMenuBiometricsTest.tsx:
   • press the Biometrics Test button
   • assert the Test Tools modal close path is called first
   • invoke the afterTransition callback
   • assert navigation then goes to ROUTES.MULTIFACTOR_AUTHENTICATION_BIOMETRICS_TEST

Manual regression test:

• On iOS, open the hidden Test Tools menu with four fingers.
• Tap Biometrics Test.
• Verify the Test Tools menu closes and the “Let’s verify it’s you” biometrics flow is visible.

What alternative solutions did you explore? (Optional)

I considered closing the Test Tools modal from BiometricsTestPage, but that is too late because the stale modal has already been left in the navigation stack. I also would not use the generic Modal.close() path here because the Test Tools menu is controlled by a navigation modal route, and its existing close behavior already uses Navigation.goBack() with the backTo param.