[Due for payment 2026-01-05] [$250] Expensify Card - RHP back button loops between magic code and "Who needs a step?" step

[jponikarchuk]

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.2.75-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #76241
Email or phone of affected tester (no customers): applausetester+khcategory20@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Mac 26.1 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

• Workspace is set up with Expensify Card feature.

1. Go to staging.new.expensify.com
2. Go to workspace settings > Expensify Card.
3. Click Issue card.
4. Go through the flow and reach the confirm page.
5. On confirm page, click Issue card.
6. On magic code page, click RHP back button until it reaches the first page - Who needs a card?
7. Click RHP back button again.
8. Click RHP back buton.

Expected Result:

In Step 7, RHP will close.
In Step 8, RHP will close.

Actual Result:

In Step 7, RHP reopens magic code page.
In Step 8, RHP reopens Who needs a card? step.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021999162249337136654
• Upwork Job ID: 1999162249337136654
• Last Price Increase: 2026-01-12

Issue Owner

Current Issue Owner: @JmillsExpensify

[melvin-bot]

Triggered auto assignment to @JmillsExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Triggered auto assignment to @puneetlath (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[samranahm]

Proposal

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

Expensify Card - RHP back button loops between magic code and "Who needs a step?" step

What is the root cause of that problem?

When clicking the back button from the magic code page, it calls handleClose which navigates to WORKSPACE_EXPENSIFY_CARD_ISSUE_NEW, which reopens the IssueNewCardPage. Since the issueNewCard state still has a currentStep, the flow renders that step again. When the back button is clicked from AssigneeStep, handleBackButtonPress calls Navigation.goBack() followed by clearIssueNewCardFlow(policyID). But clearIssueNewCardFlow only clears the data, it doesn't close the modal, so Navigation.goBack() navigates back to the magic code page, which then reopens the assignee step again, creating a loop.

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

We should ensure that when we're at the first step AssigneeStep and not editing, we should close the RHP flow entirely with closeRHPFlow instead of just navigating back.

const handleBackButtonPress = () => {
    if (isEditing) {
        setIssueNewCardStepAndData({step: CONST.EXPENSIFY_CARD.STEP.CONFIRMATION, isEditing: false, policyID});
        return;
    }
    clearIssueNewCardFlow(policyID);
    Navigation.closeRHPFlow();
};

here

App/src/pages/workspace/expensifyCard/issueNew/AssigneeStep.tsx

Lines 109 to 116 in 4c774c6

	const handleBackButtonPress = () => {
	if (isEditing) {
	setIssueNewCardStepAndData({step: CONST.EXPENSIFY_CARD.STEP.CONFIRMATION, isEditing: false, policyID});
	return;
	}
	Navigation.goBack();
	clearIssueNewCardFlow(policyID);
	};

and modify handleClose to call clearIssueNewCardFlow(policyID) before navigating back.
This ensures when navigating back from the magic code page, the flow state is cleared first, preventing the IssueNewCardPage from reopening at a specific step

const handleClose = useCallback(() => {
    resetValidateActionCodeSent();
    clearIssueNewCardFlow(policyID);
    Navigation.navigate(ROUTES.WORKSPACE_EXPENSIFY_CARD_ISSUE_NEW.getRoute(policyID, backTo));
}, [policyID, backTo]);

here

App/src/pages/workspace/expensifyCard/issueNew/IssueNewCardConfirmMagicCodePage.tsx

Lines 56 to 59 in 4c774c6

	const handleClose = useCallback(() => {
	resetValidateActionCodeSent();
	Navigation.navigate(ROUTES.WORKSPACE_EXPENSIFY_CARD_ISSUE_NEW.getRoute(policyID, backTo));
	}, [policyID, backTo]);

What alternative solutions did you explore? (Optional)

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.