Fix Expensify Card transactions incorrectly showing "Deleted Card" by blimpich · Pull Request #87540 · Expensify/App

blimpich · 2026-04-09T20:57:35Z

Explanation of Change

doesCardFeedExist() calls getOriginalCompanyFeeds(), which intentionally filters out entries where key === CONST.EXPENSIFY_CARD.BANK (since Expensify Cards aren't third-party company card feeds). This means doesCardFeedExist('Expensify Card', cardFeeds) always returns false, and any transaction made on an Expensify Card gets isCardFeedDeleted: true, causing the UI to display "Deleted card" / "Deleted Feed".

The fix adds an early return in doesCardFeedExist for Expensify Card feeds, since they are a native card product that cannot be disconnected or deleted like a third-party feed. The type signature is also widened from CompanyCardFeed to CardFeed to properly accept the Expensify Card bank value without requiring a type cast at call sites.

Fixed Issues

$ #87098
$ #82814
PROPOSAL: N/A

Tests

Log in as a user with Expensify Card transactions
Open New Expensify and navigate to your expense list or a report containing Expensify Card transactions
Verify the card column shows the correct card name (e.g. "Expensify Card") instead of "Deleted card"
Navigate to Accounting > Reports and view "Unapproved Card" or "Reconciliation: Expensify Card" groupings
Verify the feed column shows the correct feed name instead of "Deleted Feed"
Verify that transactions made on actual third-party company cards still show correct card names
Verify that transactions from a genuinely deleted third-party feed still correctly show "Deleted card"

Verify that no errors appear in the JS console

Offline tests

N/A — This is a display logic fix that does not involve network requests or offline state. The doesCardFeedExist function operates on locally cached Onyx data.

QA Steps

Same as Tests (steps 1-7 above, on staging).

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Before fix

After fix

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

melvin-bot · 2026-04-09T21:25:07Z

@situchan Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

situchan · 2026-04-09T21:51:04Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified there are no new alerts related to the canBeMissing param for useOnyx
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

Android: mWeb Chrome

iOS: HybridApp

ios.mov

iOS: mWeb Safari

MacOS: Chrome / Safari

`Expenses` section

before:

Screen.Recording.2026-04-10.at.3.46.29.AM.mov

after:

Screen.Recording.2026-04-10.at.3.49.29.AM.mov

`group-by:card` filter

before:

after:

melvin-bot · 2026-04-09T21:52:29Z

@arosiclair Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

situchan · 2026-04-09T21:57:56Z

Modifying doesCardFeedExist to special-case Expensify Card: Possible but less clean — doesCardFeedExist is specifically about company card feeds, and mixing in Expensify Card awareness would blur that abstraction.

Modifying doesCardFeedExist to not use getOriginalCompanyFeeds: This would work but risks side effects since getOriginalCompanyFeeds intentionally excludes Expensify Cards from the company card feed list for display purposes.

Tests well but what do you think of this concern? I think it's fine.

blimpich · 2026-04-09T22:41:38Z

Modifying doesCardFeedExist to special-case Expensify Card: Possible but less clean — doesCardFeedExist is specifically about company card feeds, and mixing in Expensify Card awareness would blur that abstraction.

Modifying doesCardFeedExist to not use getOriginalCompanyFeeds: This would work but risks side effects since getOriginalCompanyFeeds intentionally excludes Expensify Cards from the company card feed list for display purposes.

Tests well but what do you think of this concern? I think it's fine.

Yeah I considered that but I think this fix is the most concise and fixes the issue everywhere it will present. I didn't feel like the "best" way to fix it at first but after looking at the alternatives I thought it was the best.

github-actions · 2026-04-09T22:43:34Z

🚧 @blimpich has triggered a test Expensify/App build. You can view the workflow run here.

github-actions · 2026-04-09T22:48:39Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #87540.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-be63e22-b0990c7-6d19a789025720ce9b279fd461cca7e90674add1/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-be63e22-b0990c7-7769e75afc832ceb494d147f4334bb187b08273c/index.html

Web 🕸️
https://87540.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

…Positive (cherry picked from commit be63e22) (cherry-picked to staging by blimpich)

OSBotify · 2026-04-09T22:52:33Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2026-04-09T23:28:16Z

🚀 Cherry-picked to staging by https://github.com/blimpich in version: 9.3.55-2 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

Android
iOS

MelvinBot · 2026-04-09T23:29:36Z

No help site changes required.

This PR is a bug fix in CardUtils.doesCardFeedExist() that corrects Expensify Card transactions from incorrectly displaying "Deleted card" / "Deleted Feed." It does not introduce any new features, change workflows, or alter settings/terminology that would need help site documentation updates.

…Positive (cherry picked from commit be63e22) (cherry-picked to production by blimpich)

OSBotify · 2026-04-10T00:16:41Z

🚀 Deployed to production by https://github.com/roryabraham in version: 9.3.56-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

Android
iOS

OSBotify · 2026-04-10T00:49:33Z

🚀 Cherry-picked to staging by https://github.com/blimpich in version: 9.3.57-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

Android
iOS

Fix doesCardFeedExist returning false for Expensify Card transactions

83ae0c9

melvin-bot bot assigned blimpich Apr 9, 2026

blimpich marked this pull request as ready for review April 9, 2026 21:25

blimpich requested review from a team as code owners April 9, 2026 21:25

melvin-bot bot requested review from joekaufmanexpensify and situchan and removed request for a team April 9, 2026 21:25

melvin-bot bot removed the request for review from a team April 9, 2026 21:25

blimpich changed the title ~~Fix Expensify Card transactions incorrectly showing Deleted Card~~ Fix Expensify Card transactions incorrectly showing "Deleted Card" Apr 9, 2026

situchan approved these changes Apr 9, 2026

View reviewed changes

melvin-bot bot requested a review from arosiclair April 9, 2026 21:52

srikarparsi approved these changes Apr 9, 2026

View reviewed changes

blimpich merged commit be63e22 into main Apr 9, 2026
49 of 51 checks passed

blimpich deleted the blimpich-fixDeletedCardFalsePositive branch April 9, 2026 22:43

OSBotify pushed a commit that referenced this pull request Apr 9, 2026

Merge pull request #87540 from Expensify/blimpich-fixDeletedCardFalse…

6cf9e74

…Positive (cherry picked from commit be63e22) (cherry-picked to staging by blimpich)

OSBotify added the CP Staging marks PRs that have been CP'd to staging label Apr 9, 2026

OSBotify mentioned this pull request Apr 9, 2026

Deploy Checklist: New Expensify 2026-04-09 #87435

Open

66 tasks

blimpich added the CP Production label Apr 9, 2026

OSBotify pushed a commit that referenced this pull request Apr 9, 2026

Merge pull request #87540 from Expensify/blimpich-fixDeletedCardFalse…

95c0b3b

…Positive (cherry picked from commit be63e22) (cherry-picked to production by blimpich)

Conversation

blimpich commented Apr 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Before fix

After fix

Uh oh!

melvin-bot bot commented Apr 9, 2026

Uh oh!

situchan commented Apr 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Expenses section

group-by:card filter

Uh oh!

melvin-bot bot commented Apr 9, 2026

Uh oh!

situchan commented Apr 9, 2026

Uh oh!

blimpich commented Apr 9, 2026

Uh oh!

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

github-actions bot commented Apr 9, 2026

Uh oh!

OSBotify commented Apr 9, 2026

Uh oh!

OSBotify commented Apr 9, 2026

Uh oh!

MelvinBot commented Apr 9, 2026

Uh oh!

OSBotify commented Apr 10, 2026

Uh oh!

OSBotify commented Apr 10, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

blimpich commented Apr 9, 2026 •

edited

Loading

situchan commented Apr 9, 2026 •

edited

Loading

`Expenses` section

`group-by:card` filter