[$250] Company card - Back button on Card details reopens Card details after returning from QBO export

[lanitochka17]

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.91-1
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-2633/folder/13176706/41236851/1103228308
Email or phone of affected tester (no customers): applausetester+020101abc@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: Mac 26.1 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

• Assign a company card to any workspace member.
• Workspace is connected to QBO.

1. Go to staging.new.expensify.com
2. Go to workspace settings > Members.
3. Click on the member with company card.
4. Click on the card.
5. Click QuickBooks Online credit card export.
6. Select any option.
7. Click RHP back button on card details page.
8. Click RHP back button again.

Expected Result:

In Step 7, RHP will return to member profile.

Actual Result:

In Step 7, RHP reopens card details page.
In Step 8, RHP returns to member profile.

Similar issue was fixed previously - #62197

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7040673_1767373074396.9.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022008213301653535948
• Upwork Job ID: 2008213301653535948
• Last Price Increase: 2026-01-05

Issue Owner

Current Issue Owner: @bernhardoj

[melvin-bot]

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

[samranahm]

Proposal

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

When navigating through company card settings (Member > Card Details > QBO Export > Select Option), clicking the back button on the Card Details page incorrectly reopens the Card Details page instead of returning to the Member Profile page. Users must click back twice to reach the Member Profile.

What is the root cause of that problem?

When the user selects an export option and navigates back to Card Details, the code preserves the backTo parameter from the current route and passes it again to the Card Details route.

Specifically, in updateExportAccount callback and onBackButtonPress callback

• The navigation back to Card Details does not include the backTo parameter
• When user then clicks back on Card Details, the backTo value is stale or points to an incorrect route

This creates a navigation loop where the back button doesn't properly restore the original navigation stack.

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

We should ensure that when navigating back from the export page to the Card Details page, we preserve the original backTo parameter so that the Card Details page knows where to return when its back button is pressed.

Changes needed in WorkspaceCompanyCardAccountSelectCardPage

1. In the updateExportAccount callback, when navigating back to Card Details after selecting an export option, pass the backTo parameter to maintain the correct navigation chain.

      Navigation.goBack(ROUTES.WORKSPACE_COMPANY_CARD_DETAILS.getRoute(policyID, feed, cardID, backTo));
  },
  [exportMenuItem?.exportType, domainOrWorkspaceAccountID, cardID, policyID, feed, defaultCard, backTo],

App/src/pages/workspace/companyCards/WorkspaceCompanyCardAccountSelectCardPage.tsx

Lines 85 to 87 in f7265ef

	Navigation.goBack(ROUTES.WORKSPACE_COMPANY_CARD_DETAILS.getRoute(policyID, feed, cardID));
	},
	[exportMenuItem?.exportType, domainOrWorkspaceAccountID, cardID, policyID, feed, defaultCard],

2. Add backTo to the dependency array of the updateExportAccount callback so it has access to the current backTo value.

3. In the onBackButtonPress callback, remove the {compareParams: false} option as it's not necessary and cause navigation issues.

  onBackButtonPress={() => Navigation.goBack(ROUTES.WORKSPACE_COMPANY_CARD_DETAILS.getRoute(policyID, feed, cardID, backTo))}

This ensures the navigation flow works correctly:

• Member Profile > Card Details (backTo = Member Profile)
• Card Details > Export Page (backTo = Member Profile)
• Export Page > Card Details (backTo = Member Profile preserved)
• Card Details > Member Profile (using preserved 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.

[ShridharGoel]

Proposal

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

When a workspace admin selects a QuickBooks Online export account for a company card and taps the back button in the right-hand panel, the app opens a fresh card details page instead of returning to the existing member profile panel.

What is the root cause of that problem?

The export account picker goes back to the card details route without preserving the prior backTo target or ignoring param comparison, so navigation treats it as a new route stack entry rather than reusing the existing one.

App/src/pages/workspace/companyCards/WorkspaceCompanyCardAccountSelectCardPage.tsx

Lines 76 to 88 in f7265ef

	const updateExportAccount = useCallback(
	({value}: SelectorType) => {
	if (!exportMenuItem?.exportType) {
	return;
	}
	const isDefaultCardSelected = value === defaultCard;
	const exportValue = isDefaultCardSelected ? CONST.COMPANY_CARDS.DEFAULT_EXPORT_TYPE : value;
	setCompanyCardExportAccount(policyID, domainOrWorkspaceAccountID, cardID, exportMenuItem.exportType, exportValue, getCompanyCardFeed(feed));
	Navigation.goBack(ROUTES.WORKSPACE_COMPANY_CARD_DETAILS.getRoute(policyID, feed, cardID));
	},
	[exportMenuItem?.exportType, domainOrWorkspaceAccountID, cardID, policyID, feed, defaultCard],
	);

.

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

Update the export account picker to navigate back to the existing card details screen while retaining the original back target and skipping param comparison, ensuring a single back action returns to the member profile.

    const updateExportAccount = useCallback(
        ({value}: SelectorType) => {
            ....

            Navigation.goBack(ROUTES.WORKSPACE_COMPANY_CARD_DETAILS.getRoute(policyID, feed, cardID, backTo), {compareParams: false});
        },
        [exportMenuItem?.exportType, domainOrWorkspaceAccountID, cardID, policyID, feed, defaultCard, backTo],
    );

[melvin-bot]

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

[melvin-bot]

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