[Due for payment 2026-05-15] [$250] Remove showRedirectToExpensifyClassicModal logic

[MelvinBot]

Problem

Users are occasionally seeing a "Redirect to Expensify Classic" modal when clicking the Create Expense button from the Home page, even though they are on a group workspace and should be able to use NewDot.

The showRedirectToExpensifyClassicModal logic was originally added to block users from creating, tracking, or submitting expenses from NewDot if:

1. They are on at least one group policy
2. None of their group policies have isPolicyExpenseChatEnabled: true

This was relevant during the migration period, but now all group workspaces have completed the data migration and have isPolicyExpenseChatEnabled: true. The guard is no longer needed and may trigger incorrectly due to race conditions (e.g., OpenApp data not fully loaded yet).

Solution

Remove the showRedirectToExpensifyClassicModal logic entirely, including:

• The useRedirectToExpensifyClassic hook and its usage
• All call sites that invoke showRedirectToExpensifyClassicModal, including in QuickCreationActionsBar
• The associated modal component and any related dead code

Slack thread: https://expensify.slack.com/archives/C07NMDKEFMH/p1777061645458519

Issue Owner

Current Issue Owner: @mallenexpensify

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022048784069713016985
• Upwork Job ID: 2048784069713016985
• Last Price Increase: 2026-04-27

[puneetlath]

@MelvinBot investigate this.

[MelvinBot]

Proposal

Problem: The showRedirectToExpensifyClassicModal guard blocks expense/report/invoice creation when all group policies have isPolicyExpenseChatEnabled: false. Since all group workspaces have now completed data migration, this guard is obsolete and can fire incorrectly due to race conditions (e.g., OpenApp data not yet loaded).

Solution: Remove the entire redirect-to-classic feature across ~31 files. The change touches three layers: (1) core logic (hook, selector, utility, Onyx key, modal component), (2) call sites in FAB menu items / search / quick-creation bar, and (3) translations.

Files to DELETE entirely (7 files):

File	Purpose
useRedirectToExpensifyClassic.ts	Core hook
BaseConfirmNavigateExpensifyClassicModal.tsx	Modal component
ConfirmNavigateExpensifyClassicModal/index.tsx	Web export
ConfirmNavigateExpensifyClassicModal/index.native.tsx	Native export
isOpenConfirmNavigateExpensifyClassicModal.ts	Onyx action
useRedirectToExpensifyClassicTest.ts	Unit test
BaseConfirmNavigateExpensifyClassicModalTest.tsx	Unit test

Files to MODIFY (~24 files):

Core plumbing:

• ONYXKEYS.ts:703,1541 — remove IS_OPEN_CONFIRM_NAVIGATE_EXPENSIFY_CLASSIC_MODAL_OPEN key and its type mapping
• selectors/Policy.ts:93 — remove shouldRedirectToExpensifyClassicSelector and its export
• libs/PolicyUtils.ts:1862-1885 — remove areAllGroupPoliciesExpenseChatDisabled and its export
• AuthScreens.tsx — remove <OpenConfirmNavigateExpensifyClassicModal /> import and JSX

FAB menu items (remove redirect guard blocks from onPress):

• ExpenseMenuItem.tsx
• CreateReportMenuItem.tsx
• InvoiceMenuItem.tsx
• TrackDistanceMenuItem.tsx
• useScanActions.ts

Search/Create button components:

• SearchActionsBarCreateButton.tsx — remove inline redirect modal logic
• QuickCreationActionsBar/index.tsx — remove redirect modal callback and guards in handleExpense, handleReport, handleDistance
• EmptySearchView.tsx — remove redirect logic
• useSearchTypeMenuSections.ts — remove shouldRedirectToExpensifyClassic computation and param passing
• SearchUIUtils.ts — remove shouldRedirectToExpensifyClassic from TypeMenuSectionsParams type and guard block

Translations (remove sidebarScreen.redirectToExpensifyClassicModal in all 10 language files):

• en.ts, es.ts, fr.ts, de.ts, it.ts, ja.ts, nl.ts, pl.ts, pt-BR.ts, zh-hans.ts

What is NOT dead code (keep):

• isPolicyExpenseChatEnabled on the Policy type — used in ~60 files for workspace selection and other features
• shouldHideOldAppRedirect in TryNewDotUtils — used by 7 other files unrelated to this feature
• groupPaidPoliciesWithExpenseChatEnabledSelector — serves workspace filtering independent of the redirect

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

[melvin-bot]

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

[wildan-m]

Proposal

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

The "Redirect to Expensify Classic" modal can incorrectly intercept clicks on Create Expense (and the other quick-action buttons) on a group workspace, even though every group workspace now has isPolicyExpenseChatEnabled: true. The migration that motivated this guard is finished, so the guard is dead code that only causes false positives during transient OpenApp loading states.

What is the root cause of that problem?

There is still a runtime check that asks "are ALL of my group policies chat-disabled?" and, if so, opens a confirm modal that exits NewDot back to Expensify Classic. The check is implemented by areAllGroupPoliciesExpenseChatDisabled in src/libs/PolicyUtils.ts and surfaced through shouldRedirectToExpensifyClassicSelector in src/selectors/Policy.ts:

App/src/libs/PolicyUtils.ts

Lines 1862 to 1880 in 71a4eb6

	function areAllGroupPoliciesExpenseChatDisabled(policies: OnyxCollection<Policy> | null) {
	let foundGroupPolicy = false;
	for (const policy of Object.values(policies ?? {})) {
	if (!policy || !isPaidGroupPolicy(policy)) {
	continue;
	}
	if (policy.isJoinRequestPending || !shouldShowPolicy(policy, false, undefined)) {
	continue;
	}
	foundGroupPolicy = true;
	if (policy.isPolicyExpenseChatEnabled) {
	return false;
	}
	}
	if (!foundGroupPolicy) {

App/src/selectors/Policy.ts

Line 93 in 71a4eb6

const shouldRedirectToExpensifyClassicSelector = (policies: OnyxCollection<Policy>) => areAllGroupPoliciesExpenseChatDisabled(policies);

The hook that wraps this and shows the modal is useRedirectToExpensifyClassic:

App/src/pages/inbox/sidebar/FABPopoverContent/useRedirectToExpensifyClassic.ts

Lines 31 to 69 in 71a4eb6

	function useRedirectToExpensifyClassic() {
	const {translate} = useLocalize();
	const {showConfirmModal} = useConfirmModal();
	const [isTrackingGPS = false] = useOnyx(ONYXKEYS.GPS_DRAFT_DETAILS, {selector: isTrackingSelector});
	const [tryNewDot, tryNewDotMetadata] = useOnyx(ONYXKEYS.NVP_TRY_NEW_DOT);
	/**
	* There are scenarios where users who have not yet had their group workspace-chats in NewDot (isPolicyExpenseChatEnabled). In those scenarios, things can get confusing if they try to submit/track expenses. To address this, we block them from Creating, Tracking, Submitting expenses from NewDot if they are:
	* 1. on at least one group policy
	* 2. none of the group policies they are a member of have isPolicyExpenseChatEnabled=true
	*/
	const [shouldRedirectToExpensifyClassic = false] = useOnyx(ONYXKEYS.COLLECTION.POLICY, {selector: shouldRedirectToExpensifyClassicSelector});
	const isLoadingTryNewDot = isLoadingOnyxValue(tryNewDotMetadata);
	const canRedirectToExpensifyClassic = shouldRedirectToExpensifyClassic && !shouldHideOldAppRedirect(tryNewDot, isLoadingTryNewDot, CONFIG.IS_HYBRID_APP);
	const canUseAction = !shouldRedirectToExpensifyClassic || canRedirectToExpensifyClassic;
	const showRedirectToExpensifyClassicModal = async () => {
	if (!canRedirectToExpensifyClassic) {
	return;
	}
	const {action} = await showConfirmModal({
	title: translate('sidebarScreen.redirectToExpensifyClassicModal.title'),
	prompt: translate('sidebarScreen.redirectToExpensifyClassicModal.description'),
	confirmText: translate('exitSurvey.goToExpensifyClassic'),
	cancelText: translate('common.cancel'),
	});
	if (action !== ModalActions.CONFIRM) {
	return;
	}
	if (CONFIG.IS_HYBRID_APP) {
	closeReactNativeApp({shouldSetNVP: true, isTrackingGPS});
	return;
	}
	openOldDotLink(CONST.OLDDOT_URLS.INBOX);
	};
	return {shouldRedirectToExpensifyClassic, canRedirectToExpensifyClassic, canUseAction, showRedirectToExpensifyClassicModal};
	}

Two more places re-implement the same shouldRedirectToExpensifyClassic + modal pair inline (instead of using the hook), which is why deleting the hook alone is not enough:

App/src/components/Navigation/QuickCreationActionsBar/index.tsx

Lines 78 to 106 in 71a4eb6

	const shouldRedirectToExpensifyClassic = useMemo(() => areAllGroupPoliciesExpenseChatDisabled((allPolicies as OnyxCollection<OnyxTypes.Policy>) ?? {}), [allPolicies]);
	const travelEnabledPolicy = useMemo(() => Object.values(allPolicies ?? {}).find((policy) => !!policy?.isTravelEnabled), [allPolicies]);
	const shouldShowBookTravel = !!travelEnabledPolicy;
	const isBlockedFromSpotnanaTravel = Permissions.isBetaEnabled(CONST.BETAS.PREVENT_SPOTNANA_TRAVEL, allBetas);
	const primaryContactMethod = primaryLogin ?? session?.email ?? '';
	const isTravelReady = useMemo(() => {
	if (!!isBlockedFromSpotnanaTravel || !primaryContactMethod || Str.isSMSLogin(primaryContactMethod) || !isPaidGroupPolicy(travelEnabledPolicy)) {
	return false;
	}
	const isPolicyProvisioned = travelEnabledPolicy?.travelSettings?.spotnanaCompanyID ?? travelEnabledPolicy?.travelSettings?.associatedTravelDomainAccountID;
	return travelEnabledPolicy?.travelSettings?.hasAcceptedTerms ?? (travelSettings?.hasAcceptedTerms && isPolicyProvisioned);
	}, [travelEnabledPolicy, isBlockedFromSpotnanaTravel, primaryContactMethod, travelSettings?.hasAcceptedTerms]);
	const showRedirectToExpensifyClassicModal = useCallback(async () => {
	const {action} = await showConfirmModal({
	title: translate('sidebarScreen.redirectToExpensifyClassicModal.title'),
	prompt: translate('sidebarScreen.redirectToExpensifyClassicModal.description'),
	confirmText: translate('exitSurvey.goToExpensifyClassic'),
	cancelText: translate('common.cancel'),
	});
	if (action === ModalActions.CONFIRM) {
	openOldDotLink(CONST.OLDDOT_URLS.INBOX);
	}
	}, [showConfirmModal, translate]);

App/src/components/Search/SearchPageHeader/SearchActionsBarCreateButton.tsx

Lines 68 to 92 in 71a4eb6

	const shouldRedirectToExpensifyClassic = useMemo(() => {
	return areAllGroupPoliciesExpenseChatDisabled((allPolicies as OnyxCollection<OnyxTypes.Policy>) ?? {});
	}, [allPolicies]);
	const defaultChatEnabledPolicy = useMemo(
	() => getDefaultChatEnabledPolicy(groupPoliciesWithChatEnabled as Array<OnyxEntry<OnyxTypes.Policy>>, activePolicy),
	[activePolicy, groupPoliciesWithChatEnabled],
	);
	const defaultChatEnabledPolicyID = defaultChatEnabledPolicy?.id;
	const hasEmptyReport = useHasEmptyReportsForPolicy(defaultChatEnabledPolicyID);
	const [hasDismissedEmptyReportsConfirmation] = useOnyx(ONYXKEYS.NVP_EMPTY_REPORTS_CONFIRMATION_DISMISSED);
	const shouldShowEmptyReportConfirmationForDefaultChatEnabledPolicy = hasEmptyReport && hasDismissedEmptyReportsConfirmation !== true;
	const showRedirectToExpensifyClassicModal = useCallback(async () => {
	const {action} = await showConfirmModal({
	title: translate('sidebarScreen.redirectToExpensifyClassicModal.title'),
	prompt: translate('sidebarScreen.redirectToExpensifyClassicModal.description'),
	confirmText: translate('exitSurvey.goToExpensifyClassic'),
	cancelText: translate('common.cancel'),
	});
	if (action === ModalActions.CONFIRM) {
	openOldDotLink(CONST.OLDDOT_URLS.INBOX);
	}
	}, [showConfirmModal, translate]);

App/src/pages/Search/EmptySearchView.tsx

Lines 157 to 233 in 71a4eb6

	const shouldRedirectToExpensifyClassic = areAllGroupPoliciesExpenseChatDisabled(allPolicies ?? {});
	const defaultChatEnabledPolicy = getDefaultChatEnabledPolicy(groupPoliciesWithChatEnabled as Array<OnyxEntry<Policy>>, activePolicy);
	const defaultChatEnabledPolicyID = defaultChatEnabledPolicy?.id;
	const hasEmptyReport = useHasEmptyReportsForPolicy(defaultChatEnabledPolicyID);
	const [hasDismissedEmptyReportsConfirmation] = useOnyx(ONYXKEYS.NVP_EMPTY_REPORTS_CONFIRMATION_DISMISSED);
	const shouldShowEmptyReportConfirmation = hasEmptyReport && hasDismissedEmptyReportsConfirmation !== true;
	const filteredPolicyID = queryJSON?.policyID;
	let isFilteredWorkspaceAccessible = true;
	if (filteredPolicyID) {
	const policyIDToCheck = Array.isArray(filteredPolicyID) ? filteredPolicyID.at(0) : filteredPolicyID;
	const filteredPolicy = allPolicies?.[`${ONYXKEYS.COLLECTION.POLICY}${policyIDToCheck}`];
	isFilteredWorkspaceAccessible = !!filteredPolicy;
	}
	const handleCreateWorkspaceReport = (shouldDismissEmptyReportsConfirmation?: boolean) => {
	if (!defaultChatEnabledPolicy?.id) {
	return;
	}
	const {reportID: createdReportID} = createNewReport(
	currentUserPersonalDetails,
	hasViolations,
	isASAPSubmitBetaEnabled,
	defaultChatEnabledPolicy,
	betas,
	false,
	shouldDismissEmptyReportsConfirmation,
	);
	Navigation.setNavigationActionToMicrotaskQueue(() => {
	Navigation.navigate(
	ROUTES.SEARCH_MONEY_REQUEST_REPORT.getRoute({
	reportID: createdReportID,
	backTo: Navigation.getActiveRoute(),
	}),
	);
	});
	};
	const {openCreateReportConfirmation: openCreateReportFromSearch} = useCreateEmptyReportConfirmation({
	policyID: defaultChatEnabledPolicyID,
	policyName: defaultChatEnabledPolicy?.name ?? '',
	onConfirm: handleCreateWorkspaceReport,
	});
	const handleCreateReportClick = () => {
	if (shouldShowEmptyReportConfirmation) {
	openCreateReportFromSearch();
	} else {
	handleCreateWorkspaceReport(false);
	}
	};
	const handleRedirectToExpensifyClassic = () => {
	showConfirmModal({
	prompt: translate('sidebarScreen.redirectToExpensifyClassicModal.description'),
	title: translate('sidebarScreen.redirectToExpensifyClassicModal.title'),
	confirmText: translate('exitSurvey.goToExpensifyClassic'),
	cancelText: translate('common.cancel'),
	}).then((result) => {
	if (result.action !== ModalActions.CONFIRM) {
	return;
	}
	openOldDotLink(CONST.OLDDOT_URLS.INBOX);
	});
	};
	const handleCreateMoneyRequest = (iouType: typeof CONST.IOU.TYPE.CREATE | typeof CONST.IOU.TYPE.INVOICE) => {
	interceptAnonymousUser(() => {
	if (shouldRedirectToExpensifyClassic) {
	handleRedirectToExpensifyClassic();
	return;
	}
	startMoneyRequest(iouType, generateReportID(), draftTransactionIDs);

Because the predicate now always evaluates to false in production (every group workspace has isPolicyExpenseChatEnabled: true), the modal can only ever appear during a transient state where the policy data has not finished loading from OpenApp. That is the spurious "Redirect to Classic" modal users are reporting.

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

Delete the predicate, the hook, the inline reimplementations, and every gate that depended on them.

1. Delete src/pages/inbox/sidebar/FABPopoverContent/useRedirectToExpensifyClassic.ts entirely. The hook is the only consumer of shouldHideOldAppRedirect for the FAB-button flow, so the per-callsite NVP_TRY_NEW_DOT subscription disappears with it. Keep BaseConfirmNavigateExpensifyClassicModal untouched — it is a different modal triggered by a separate Onyx flag (IS_OPEN_CONFIRM_NAVIGATE_EXPENSIFY_CLASSIC_MODAL_OPEN) and is not the modal users are seeing on Create Expense.

2. The deleted file currently re-exports two helpers used elsewhere:

   • policyMapper (used by InvoiceMenuItem.tsx and NewWorkspaceMenuItem.tsx to feed useMappedPolicies)
   • PolicySelector (used as a type in src/libs/actions/Policy/Policy.ts)

   Move both to a small new module, e.g. src/pages/inbox/sidebar/FABPopoverContent/policyMapper.ts, and update the three import sites. They have no behavioural relationship with the redirect logic — they are only colocated here for historical reasons.

3. Remove the redirect branch from every callsite that currently uses the hook. In each of these files, drop the destructured shouldRedirectToExpensifyClassic, canRedirectToExpensifyClassic, canUseAction, and showRedirectToExpensifyClassicModal values, delete the if (shouldRedirectToExpensifyClassic) { … return; } early-return, and tighten the visibility prop:

   • src/pages/inbox/sidebar/FABPopoverContent/menuItems/ExpenseMenuItem.tsx — isVisible={canUseAction} becomes always-visible (isVisible prop removed or hard-coded true); also drop shouldCallAfterModalHide={canRedirectToExpensifyClassic || shouldUseNarrowLayout} to just shouldCallAfterModalHide={shouldUseNarrowLayout}.

   • src/pages/inbox/sidebar/FABPopoverContent/menuItems/InvoiceMenuItem.tsx — isVisible={canSendInvoice && canUseAction} becomes isVisible={canSendInvoice}; same shouldCallAfterModalHide simplification.

   • src/pages/inbox/sidebar/FABPopoverContent/menuItems/TrackDistanceMenuItem.tsx — isVisible={canUseAction} removed; redirect early-return removed.

   • src/pages/inbox/sidebar/FABPopoverContent/menuItems/CreateReportMenuItem.tsx — isVisible={canRedirectToExpensifyClassic || groupPoliciesWithChatEnabled.length > 0} becomes isVisible={groupPoliciesWithChatEnabled.length > 0}; redirect branch in onPress removed.

   • src/pages/inbox/sidebar/FABPopoverContent/useScanActions.ts — drop the redirect early-return inside startScan and the canUseAction field from the returned object. Then update its only consumer:

     App/src/pages/inbox/sidebar/FABPopoverContent/FABButtons.tsx

     Lines 19 to 37 in 71a4eb6

     	const {startScan, startQuickScan, canUseAction} = useScanActions();
     	return (
     	<>
     	{!shouldUseNarrowLayout && (
     	<FloatingReceiptButton
     	accessibilityLabel={translate('sidebarScreen.fabScanReceiptExplained')}
     	role={CONST.ROLE.BUTTON}
     	onPress={startQuickScan}
     	sentryLabel={CONST.SENTRY_LABEL.NAVIGATION_TAB_BAR.FLOATING_RECEIPT_BUTTON}
     	/>
     	)}
     	<FloatingActionButton
     	accessibilityLabel={translate('sidebarScreen.fabNewChatExplained')}
     	role={CONST.ROLE.BUTTON}
     	isActive={isActive}
     	ref={fabRef}
     	onPress={onPress}
     	onLongPress={canUseAction ? startScan : undefined}

     Replace onLongPress={canUseAction ? startScan : undefined} with onLongPress={startScan} and stop destructuring canUseAction.

4. Remove the inline reimplementations and their helper variables, including the useConfirmModal plumbing they require, from:

   • src/components/Navigation/QuickCreationActionsBar/index.tsx — delete the shouldRedirectToExpensifyClassic memo, the showRedirectToExpensifyClassicModal callback, the useConfirmModal import/use, the openOldDotLink/ModalActions imports if no longer referenced, the redirect early-returns in handleExpense/handleReport/handleDistance, and the corresponding entries in their dependency arrays.
   • src/components/Search/SearchPageHeader/SearchActionsBarCreateButton.tsx — same shape of cleanup: delete the shouldRedirectToExpensifyClassic memo, the showRedirectToExpensifyClassicModal callback, the redirect branch inside the "Create report" onSelected, and the dependency-array entries.
   • src/pages/Search/EmptySearchView.tsx — delete shouldRedirectToExpensifyClassic, handleRedirectToExpensifyClassic, the useConfirmModal plumbing, the redirect branch inside handleCreateMoneyRequest, and the now-unused ModalActions/openOldDotLink/CONST.OLDDOT_URLS imports if they have no other consumers in the file.
   • src/hooks/useSearchTypeMenuSections.ts — delete the local shouldRedirectToExpensifyClassic memo and stop passing it through to whatever sub-hook receives it (and remove that parameter on the receiving side).

5. Once every callsite is cleaned up:

   • Delete shouldRedirectToExpensifyClassicSelector from src/selectors/Policy.ts and remove it from the file's exports.
   • Delete areAllGroupPoliciesExpenseChatDisabled from src/libs/PolicyUtils.ts and remove it from the exports. A repo-wide grep should confirm both names have zero remaining references.

6. Translation strings under sidebarScreen.redirectToExpensifyClassicModal.{title,description} are still used by BaseConfirmNavigateExpensifyClassicModal (the unrelated, opt-in OldDot-redirect modal), so they must NOT be deleted. Same for exitSurvey.goToExpensifyClassic. No language-file changes are needed.

7. The shouldHideOldAppRedirect helper, the NVP_TRY_NEW_DOT Onyx key, and CONST.OLDDOT_URLS.INBOX all have other consumers (ScreenWrapper, InitialSettingsPage, TroubleshootPage, MergeResultPage, TwoFactorAuth/SuccessPage, BaseConfirmNavigateExpensifyClassicModal). Leave them alone — only the FAB-button-redirect-modal pathway is being removed.

After this cleanup, clicking Create Expense (and the other quick-action entry points: Track Distance, Send Invoice, Create Report, the FAB long-press scan, the Search "Create" button, and the EmptySearchView CTA) goes straight into the normal NewDot flow without any chance of a stray "Redirect to Classic" modal during the OpenApp loading window.

Compare branch: https://github.com/Expensify/App/compare/main...wildan-m:App:wildan/88951-remove-redirect-to-classic-modal?expand=1

What alternative solutions did you explore? (Optional)

Hardening the existing guard against load-time false positives — for example by waiting for OpenApp to settle before evaluating areAllGroupPoliciesExpenseChatDisabled, or by also checking tryNewDotMetadata loading state before allowing the modal to show — would mask the symptom. It still leaves the guard in place for a migration path that has already finished, so it would carry maintenance cost for a code path that has no real production trigger. Removing the guard, as the issue body recommends, is both simpler and aligns with the data shape of every current group workspace.

[melvin-bot]

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

[KJ21-ENG]

🚫 Duplicated proposal withdrawn by 🤖 ProposalPolice.

[github-actions]

⚠️ @KJ21-ENG Your proposal is a duplicate of an already existing proposal and has been automatically withdrawn to prevent spam. Please review the existing proposals before submitting a new one.

[chakmanfung18-prog]

What is the root cause of that problem?

The showRedirectToExpensifyClassicModal guard in src/pages/inbox/sidebar/FABPopoverContent/useRedirectToExpensifyClassic.ts was added during the NewDot migration to block expense/report/distance/invoice creation when a user was on group workspaces that had not yet flipped isPolicyExpenseChatEnabled to true. That migration is now complete — every group workspace ships with isPolicyExpenseChatEnabled: true — so the guard no longer protects any real state. Worse, because it derives from the policy collection in Onyx, it fires false positives whenever OpenApp has not yet hydrated the policies (the user briefly looks like they have "all group policies with chat disabled"), and incorrectly redirects them to Expensify Classic mid-action.

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

Delete the guard end-to-end and inline the now-unconditional happy path at every call site:

• Delete src/pages/inbox/sidebar/FABPopoverContent/useRedirectToExpensifyClassic.ts entirely (the hook, the policyMapper helper, and the PolicySelector type — policyMapper is only re-exported through this hook).
• src/components/Navigation/QuickCreationActionsBar/index.tsx — remove the showRedirectToExpensifyClassicModal useCallback (lines ~96-106), the shouldRedirectToExpensifyClassic memo computed from areAllGroupPoliciesExpenseChatDisabled, and the if (shouldRedirectToExpensifyClassic) { showRedirectToExpensifyClassicModal(); return; } branches in handleExpense, handleReport, and handleDistance (also drop the now-unused deps from each callback's dependency array, the useConfirmModal import/call, and the ModalActions and openOldDotLink imports if they become unused).
• src/pages/inbox/sidebar/FABPopoverContent/menuItems/ExpenseMenuItem.tsx — remove the hook import and call; replace isVisible={canUseAction} with isVisible defaulting to true (or drop the prop), drop the if (canRedirectToExpensifyClassic) { showRedirectToExpensifyClassicModal(); ... } branch, and simplify shouldCallAfterModalHide to just shouldUseNarrowLayout.
• src/pages/inbox/sidebar/FABPopoverContent/menuItems/TrackDistanceMenuItem.tsx — same treatment as ExpenseMenuItem.tsx (hook destructure, canUseAction, redirect branch).
• src/pages/inbox/sidebar/FABPopoverContent/menuItems/InvoiceMenuItem.tsx — same treatment, plus replace the policyMapper import with a local mapper (or inline the fields), since policyMapper is being deleted; reduce isVisible={canSendInvoice && canUseAction} to isVisible={canSendInvoice}.
• src/pages/inbox/sidebar/FABPopoverContent/menuItems/CreateReportMenuItem.tsx — remove the hook destructure and the if (canRedirectToExpensifyClassic) { showRedirectToExpensifyClassicModal(); ... } branch; change isVisible = canRedirectToExpensifyClassic || groupPoliciesWithChatEnabled.length > 0 to isVisible = groupPoliciesWithChatEnabled.length > 0.
• src/selectors/Policy.ts — delete shouldRedirectToExpensifyClassicSelector (line ~93) and remove it from the export {} block (line ~202); it has no other consumers once the hook is gone.
• src/libs/PolicyUtils.ts — delete areAllGroupPoliciesExpenseChatDisabled (line ~1862) and remove it from the export block (line ~2282), since QuickCreationActionsBar and shouldRedirectToExpensifyClassicSelector are its only callers.
• src/languages/en.ts, src/languages/es.ts (and any other locale files) — remove the sidebarScreen.redirectToExpensifyClassicModal.{title,description} translation entries; the only consumers are the two showConfirmModal call sites being deleted.

There is no standalone RedirectToExpensifyClassicModal.tsx component to delete — the modal is rendered inline via useConfirmModal, so removing the two call sites and the translation strings fully eliminates it.

What alternative solutions did you explore? (Optional)

One alternative is to keep the guard but harden it against the race condition — for example, gating it on a "policies fully loaded" Onyx flag (isLoading on ONYXKEYS.COLLECTION.POLICY / OpenApp completion) before treating "all group policies have isPolicyExpenseChatEnabled: false" as authoritative. Another is to put the guard behind a feature flag (beta) so it can be re-enabled if a future migration ever needs it. Both are inferior here: the guard protects a state that no longer exists in production (every group workspace now has isPolicyExpenseChatEnabled: true), so any code path that triggers it is by definition a false positive. Patching the race only delays the same false positives the next time OpenApp is slow, and a feature flag preserves a non-trivial amount of dead code (a hook, a selector, a util, translations, four menu-item branches) for a hypothetical future. Full removal is the correct call.

[melvin-bot]

📣 @chakmanfung18-prog! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Make sure you've read and understood the contributing guidelines.
2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>