Change generic card illustration fallback

[ikevin127]

Explanation of Change

The getCardFeedIcon was using the Illustrations.AmexCompanyCards as fallback for when the card feed had an unknown source (including non-AMEX cards & CSV imported cards) which on top of not making sens, was also creating UI inconsistency because the fallback illustration was smaller in size then other card illustrations used for known card sources.

This PR implements these themed generic card illustrations for the 2 edge cases described by the bug report author, more details in the issue and in Slack bug report - the changes are replacing the fallback illustration with a generic one which we want to show whenever the card's source is unknown and falls outside of our FE defined map, and also a CSV generic one for CSV imported cards.

Fixed Issues

$ #56567
PROPOSAL: #56567 (comment)

Tests

Context from Slack comment on real data the bug report author (@shawnborton) had in order to reproduce the edge cases:

• cards_2267989_ccupload17 (and similar numbers) @joekaufman we will support the csv upload in future but should we add some special icon for it?
• cards_2267989_capitalonecards - not sure how this was added but its from oldDot I think
• cards_2267989_citibusiness
• cards_2267989_csvstripe
• cards_2267989_discover.com - we support that in OldDot
• cards_2267989_vcfhsbc (and other vcf something without number)

Overall just seems like there is bunch of testing feeds and feeds from OldDot with a bit different naming convention.

Prerequisite: Ensure your account has cards added from different sources like OD / imports including CSV imported.

1. On NewDot navigate to Reports -> open Search Filters > Card.
2. Verify that for CSV imported cards (feeds including _ccupload in their name), the label reads:

• 🇺🇸 All CSV Imported Cards
• 🇪🇸 Todas las Tarjetas Importadas desde CSV

3. Verify that for all other card feeds not matching any predefined types, the label reads All like before.
4. Verify that the 2 edge case illustrations are matching the themed design (light / dark theme), see below:

• for CSV imported cards (feeds including _ccupload in their name) we display the themed CSV icon card illustration
• for all other card feeds not matching any predefined types, we display the themed bank icon card illustration

Frontend hardcoded example:

🔄 With updated CSV label:

Design coming from #56567 (comment) (source):

• Verify that no errors appear in the JS console

Offline tests

N/A.

QA Steps

Same as Tests.

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover 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 tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (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
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message: https://expensify.slack.com/archives/C01GTK53T8Q/p1740183835520569
  • 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 followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• 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
• I verified that if a function's arguments changed that all usages have also been updated correctly
• 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.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user 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.

Screenshots/Videos

Screen.Recording.2025-02-20.at.11.44.10.mov

🔄 With updated CSV label:

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

[melvin-bot]

@shawnborton @sobitneupane One of you needs to 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]

[ikevin127]

🔄 Still awaiting on decision regarding All CSV label, posted in Slack thread, quoting:

Need some help with the CSV case (_ccupload), I added return for the illustration but when it comes to the text we see in the filters page I need a decision on the text:

• All CSV (this wouldn't require translation)
• All CSV Cards
• All CSV Imported

UI Context

@mountiny Feel free to trigger an adhoc build in order for @shawnborton to test this with his account data since he was the bug report author.

[github-actions]

🚧 @dannymcclain has triggered a test build. You can view the workflow run here.

[github-actions]

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪

Android 🤖	iOS 🍎
❌ FAILED ❌	https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/57064/index.html
The QR code can't be generated, because the Android build failed
Desktop 💻	Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/57064/NewExpensify.dmg	https://57064.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀

[shawnborton]

Nice, here's what I'm seeing on my end:

Looks good to me 👍

[mountiny]

@sobitneupane can you please complete the testing? thanks!

[ikevin127]

@sobitneupane 🟢 The PR is now ready for review, only thing we're waiting on is 🇪🇸 translation confirmation.