Expensify Card- Card details page reopens after opening card details from OD & returning to ND

[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.4.16-1
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://github.com/Expensify/Mobile-Expensify/pull/13968
Email or phone of affected tester (no customers): sdjnoisdjdosijsonssjo@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: iPhone 15 Pro Max / iOS 26.5
App Component: Other

Action Performed:

Precondition:

• Enable Expensify Card in workspace settings.
• Assign a virtual card to yourself.

1. Launch Expensify app.
2. Go to Account > Troubleshoot.
3. Click Switch to Expensify Classic.
4. Open menu > Settings > Connected Cards.
5. Click Show Details.
6. Click app back button.
7. Open menu > Try New Expensify.

Expected Result:

App will return to Home.

Actual Result:

Card details page reopens after opening card details from OD and returning to ND.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7185689_1781889224714.ScreenRecording_06-20-2026_01-09-48_1.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Nathan Lemma
Bug ID: 7185689

Issue Owner

Current Issue Owner: @heekinho

[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/6fd4f67bc9ef148f1b560644b69b75a147b782f23e309724a9b8a303a5dba607

[melvin-bot]

Triggered auto assignment to @blimpich (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.

[MelvinBot]

Issue Analysis

Root Cause: This is a native HybridApp (Mobile-Expensify) bug, not an App-repo bug. When you tap Try New Expensify, the native OldDot side hands New Expensify an "initial URL" deeplink. New Expensify shadows Linking.getInitialURL() to return exactly whatever native supplies (src/setup/hybridApp/index.native.ts:5-10) and then faithfully navigates to that path. After viewing the card details in OldDot, native is sending a stale card-details deeplink (e.g. settings/wallet/card/<cardID>) instead of an empty/Home URL — so ND dutifully reopens the card details page. The regressing change is referenced as Mobile-Expensify#13968.

The App side is behaving correctly: for any specific (non-/transition) deeplink it resolves the route directly to that screen (NavigationRoot.tsx:122-161), and settings/wallet/card/:cardID is a real card-details route (ROUTES.ts:1184-1187 → ExpensifyCardPage).

Recommended Fix (outside the App repo — requires escalation): The fix belongs in Mobile-Expensify (the source of PR #13968): on Try New Expensify, native should hand ND an empty/Home URL (or clear the stored OldDot route) rather than the last-viewed OldDot card-details deeplink. Since this code is not in the Expensify/App repo, an internal engineer with Mobile-Expensify access needs to take this — I can't implement it here.

A secondary App-side hardening is possible (have NavigationRoot ignore a non-/transition initial deeplink when returning from OldDot), but that would only paper over the native behavior and risks breaking legitimate OldDot→ND deeplinks, so the native fix is the correct one.

Investigation details & evidence chain

App SHA: 6a98f2b9ba0131e295cad29078897181cf127468

Data flow:

1. User views Expensify Card details in OldDot (Connected Cards → Show Details).
2. User taps Try New Expensify.
3. Native OldDot selects an initial URL and exposes it via HybridAppModule.getInitialURL() (and/or pushes it via the url event after onURLListenerAdded — src/Expensify.tsx:244-246).
4. ND's shadowed Linking.getInitialURL() returns that URL (src/setup/hybridApp/index.native.ts:5-10).
5. React Navigation's linking config resolves the path via getAdaptedStateFromPath. For a specific (non-/transition) deeplink, NavigationRoot returns undefined so RN navigates straight to that screen (NavigationRoot.tsx:122-161).
6. The card-details path maps to a real ND route → ExpensifyCardPage reopens instead of Home.

Card-details route (the assigned-card/Wallet page that reopens):

• ROUTES.SETTINGS_WALLET_DOMAIN_CARD → path settings/wallet/card/:cardID? (ROUTES.ts:1184-1187)
• Screen Settings_Wallet_DomainCard (SCREENS.ts:212), registered with exact: true in linkingConfig/config.ts:180-183, rendered by ExpensifyCardPage (ModalStackNavigators/index.tsx:440).

Why not an App-side cause: LAST_ROUTE (an Onyx key used for responsive layout transitions) was ruled out — it is not the OD→ND handoff channel. The handoff is the native initialURL/deeplink path.

Unverified piece: The exact path string native sends could not be byte-verified because the Mobile-Expensify submodule is not checked out in this workspace. The App-side routing behavior is verified; the native URL selection (the actual defect) lives in PR #13968.

Confidence: High that the App side is not at fault and the fix belongs in Mobile-Expensify; the precise native URL string is inferred, not byte-verified.

---

This is a native (Mobile-Expensify) deploy blocker — the root cause and fix are outside the Expensify/App repo, so an internal engineer with Mobile-Expensify access should take it (start from PR Mobile-Expensify#13968). Reply with @MelvinBot <feedback> to refine this analysis.

[heekinho]

@nlemma I started testing and I think this can be unrelated.

1. In ND > Troubleshoot > Switch to Expensify Classic
2. On OD > Try New Dot

It opens the Troubleshoot page. Meaning that it will open any page that was open before.
I'll check if that's a new behavior, but please try it as well.

That said, we probably might want to always take the user to the home page, anyway, so I can open a PR to implement that.

[heekinho]

I really believe this is a pre-existing thing:

App/src/libs/Navigation/NavigationRoot.tsx

Lines 128 to 138 in e908b52

	if (shouldOpenLastVisitedPath(lastVisitedPath) && authenticated) {
	// Only skip restoration if there's a specific deep link that's not the root
	// This allows restoration when app is killed and reopened without a deep link
	const isRootPath = !path || path === '' || path === '/';
	const isSpecificDeepLink = path && !isRootPath;
	if (!isSpecificDeepLink) {
	Log.info('Restoring last visited path on app startup', false, {lastVisitedPath, initialUrl, path});
	return getAdaptedStateFromPath(lastVisitedPath);
	}
	}

Nothing related to last implemented features @nlemma. But I implemented it a small bugfix anyway: https://github.com/Expensify/Mobile-Expensify/pull/13981