[Due for payment 2025-09-23] [$250] Expensify card - Not here page when open card from another feed

[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: v9.1.87-9
Reproducible in staging?: Yes
Reproducible in production?: Yes
**If this was caught during regression testing, add the test name, ID and link from TestRail:**KI retest #65638
Email or phone of affected tester (no customers): -
Issue reported by: Applause Internal Team
Device used: Windows 11 / Chrome
App Component: Other

Action Performed:

Precondition:

1. User is logged in ND with applause.expensifail.com account.
2. Workspace A and B are set up with Expensify Card.
3. Workspace A has at least one other member other than the workspace owner.

STR:

1. Go to Workspace A settings > Expensify Card.
2. Open the Expensify Card feed selector.
3. Select the card feed from Workspace B.
4. Go to Members > Click on the member.
5. Click + New card > Go through the process of adding VIRTUAL card and reach confirmation page.
6. On the confirmation page, click Issue card.
7. Repeat steps 2-4 with feed from Workspace A
8. Go to Members > click on member
9. Click on both cards in Assigned cards

Expected Result:

Card details tab opened for both cards

Actual Result:

Card details tab opened for card from WS A.
Not here page opened for card from WS B

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/~021953484760738718185
• Upwork Job ID: 1953484760738718185
• Last Price Increase: 2025-08-14

Issue Owner

Current Issue Owner: @abekkala

[melvin-bot]

Triggered auto assignment to @abekkala (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]

@abekkala Huh... This is 4 days overdue. Who can take care of this?

[melvin-bot]

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

[melvin-bot]

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

[mukhrr]

Proposal

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

The card details page can’t find a card when opened from different feed.

What is the root cause of that problem?

Cards details was rendered based on last selected WS settings where useDefaultFundID gives it.
And in WorkspaceExpensifyCardDetailsPage.tsx cardsList were coming from last selected WS on Expensify Cards page when you selected from dropdown.

Pay attention to defaultFundID here:

const [cardsList, cardsListResult] = useOnyx(`${ONYXKEYS.COLLECTION.WORKSPACE_CARDS_LIST}${defaultFundID}_${CONST.EXPENSIFY_CARD.BANK}`, {
      selector: filterInactiveCards,
      canBeMissing: true,
});

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

We need to get all WS cards and show by cardId on details on L64 in WorkspaceExpensifyCardDetailsPage:

const card = workspaceCards?.[cardID];

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

• Card exists only under cards_<fundID>_Expensify Card: details page finds and renders it.
• Card exists only under cards_<workspaceAccountID>_Expensify Card: details page finds and renders it.
• Card exists under both keys: details page still renders the correct card.
• Card is inactive/closed: details page shows Not Found (consistent with existing filtering).
• Loading state: while WORKSPACE_CARDS_LIST is loading, page doesn’t incorrectly show Not Found.

What alternative solutions did you explore? (Optional)

I thought about passing WS settings to useDefaultFundID to prevent it from using lastSelected settings. But i guess this is a bit overhead.

[hoangzinh]

Thank you for posting proposal, @mukhrr. I will try to review it soon.