Rillet - Back button closes RHP after refreshing Card program account & Per-card account

[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.36-0
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: #95562
Email or phone of affected tester (no customers): applausetester+ssndjois2jd1@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

• Log in with Expensifail account.
• Workspace is connected to Rillet.
• Workspace has Wells Fargo direct feed with unassigned card.

1. Go to staging.new.expensify.com
2. Go to workspace settings > Accounting.
3. Click Export.
4. Enable Configure exporting to multiple accounts.
5. Click Card program account.
6. Refresh the page.
7. Click RHP back button.
8. Click Export > Per-card account.
9. Refresh the page.
10. Click RHP back button.

Expected Result:

After refreshing Card program account (Step 7) and Per-card account (Step 10), RHP back button will return to Export page.

Actual Result:

After refreshing Card program account (Step 7) and Per-card account (Step 10), RHP back button closes the page.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7210790_1784304646937.4.mp4

View all open jobs on GitHub

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

Issue Owner

Current Issue Owner: @truph01

[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/9d766b0b666452cc55a0e7c0e7aacb3868f3a50b53d779a01bc0de2d43b3c7f5

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #95562

[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]

Proposal

Root Cause

The two new pages render through ConnectionLayout without an onBackButtonPress, so they inherit its default () => Navigation.goBack() — which passes no fallback route (ConnectionLayout.tsx:111).

After a browser refresh, the RHP stack is reconstructed with only the single current screen (the Rillet routes are registered as flat siblings, not nested — config.ts:791-799). So navigationRef.canGoBack() is false, and with no fallback route goBack() cannot goUp() to Export — it dismisses the whole RHP to the Accounting pane (Navigation.ts:518-544). That is the "back closes the page" symptom.

Every sibling Rillet page that works correctly passes an explicit fallback route, e.g. RilletCompanyCardAccountPage.tsx:39,93 and even the child RilletCardProgramAccountSelector.tsx:58,115. Only the two intermediate list pages from Expensify/App#95562 were missed.

Recommended Fix

Add an onBackButtonPress with the Export fallback route to each affected ConnectionLayout page:

• RilletCardProgramAccount.tsx →
  onBackButtonPress={() => Navigation.goBack(policyID ? ROUTES.POLICY_ACCOUNTING_RILLET_EXPORT.getRoute(policyID) : undefined)}
• RilletCardAccount.tsx → same fallback to POLICY_ACCOUNTING_RILLET_EXPORT.
• ⚠️ Also fix RilletCardAccountCardList.tsx — same defect one level deeper; its back should fall back to POLICY_ACCOUNTING_RILLET_CARD_ACCOUNT. (ROUTES needs importing there.)

Navigation is already imported in all three files; ROUTES is already imported in the two parent pages.

Evidence & data flow

1. Deep-link / refresh on .../accounting/rillet/export/card-program-account.
2. linkingConfig maps the URL to RILLET_CARD_PROGRAM_ACCOUNT as a flat screen → RHP stack reconstructed with only this screen (no Export beneath).
3. Back button → HeaderWithBackButton fires ConnectionLayout's onBackButtonPress.
4. Page passes none → default () => Navigation.goBack() (ConnectionLayout.tsx:111).
5. goBack() has no backToRoute and canGoBack() is false → cannot goUp() to Export → RHP dismissed to Accounting.

Confidence: High — deterministic code-path defect, reproducible from source; matches the exact repro in the report. The flat-route registration is the standard App pattern, so the fix is the fallback route (not route nesting).

---

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