[$250] [RCA #67117] Unapproved card - “Feed:” fast filter shows duplicated “Expensify Card” #67702
Description
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.1.88-2
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: #67117
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause - Internal Team
Action Performed:
- Go to https://staging.new.expensify.com/
- Sign up with an Expensifail account
- Create a workspace
- Go to Workspace > Expensify Card > Issue new card (complete the flow and add a Regions bank account)
- Click Company Cards > Expensify Card > Issue new card > click the bank account
- After the bank account is verified, click "Got it"
- Issue a virtual card (using any data).
- Go to Company Cards > Add cards > United States > Direct feed > Other (add a Wells Fargo bank account)
- In the LHN, go to Reports > Unapproved card > “Feed:”
Expected Result:
“Feed:” fast filter should list each feed once.
Actual Result:
“Expensify Card” appears twice in the “Feed:” fast filter.
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
- MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
- MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidence
Bug6905521_1754078388955.__67117.mp4
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021973811466391405300
- Upwork Job ID: 1973811466391405300
- Last Price Increase: 2025-10-02
- Automatic offers:
- ShridharGoel | Contributor | 109001398
Activity
github-actions commentedon Aug 1, 2025
👋 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:
melvin-bot commentedon Aug 1, 2025
Triggered auto assignment to @chuckdries (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Aug 1, 2025
Triggered auto assignment to @greg-schroeder (
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 commentedon Aug 1, 2025
💬 A slack conversation has been started in #expensify-open-source
chuckdries commentedon Aug 1, 2025
Hmmm, I followed the steps exactly and it didn't break for me
56 remaining items
ikevin127 commentedon Oct 18, 2025
@ShridharGoel ☝️ Looks like some of the feeds are not even rendering anything, might be able to find these and filter them out -> then identify the duplicated Expensify Card feed more easily since it should be in the same array / object with those without names (which we don't have constants defined for, so they are not mapping to anything -> but still appear as empty).
This is definitely a tricky one!
ShridharGoel commentedon Oct 19, 2025
@lanitochka17 Can you share the latest troubleshoot data (the one which has feeds without any name in the latest screenshot) ?
ShridharGoel commentedon Oct 24, 2025
@lanitochka17 Can you check the above comment?
lanitochka17 commentedon Oct 24, 2025
Hello @ShridharGoel
the original issue is still reproducible
Device: Windows 11, Chrome
Build: v9.2.37-8
explorer_mp5t6ckHT7.mp4
troubleshoot (2).zip
luacmartins commentedon Oct 24, 2025
I think this is something weird with this particular account setup. The account does have multiple ECards assigned with different fundIDs.
But somehow they only have one card in the workspace
I'm not sure how they got to that state. cc @puneetlath I see you in the blame for some of these card changes. Do you have any idea how the above is possible? i.e. account has 1 workspace, 3 Ecards in the
cardList, but only 1 card in thecard_collection?JmillsExpensify commentedon Oct 30, 2025
Checking in on that question above @puneetlath
puneetlath commentedon Nov 4, 2025
Hmm, interesting. It sounds like it could be similar to the issue we are working on here. Where the user has multiple feeds of the same name -- one domain and one workspace. And we are only displaying one, even though there are actually two.
Where can I find the email address on the account so that I can take a look myself? Apologies if it's somewhere obvious, I tried to find it myself but didn't.
ikevin127 commentedon Nov 4, 2025
@puneetlath
applausetester+retest_n400@applause.expensifail.comseems to be the tester's account email address which can consistently reproduce the issue - extracted it from this comment data dump.puneetlath commentedon Nov 4, 2025
I'm not seeing any workspaces in that account.
@lanitochka17 would you mind putting that account back into the state where the issue is reproducible? Or letting me know another account I can log into where you are able to see the same issue.
lanitochka17 commentedon Nov 6, 2025
@puneetlath done
applausetester+retest_n400@applause.expensifail.com
luacmartins commentedon Nov 10, 2025
@puneetlath seems like the account is back. Curious for your thoughts.
luacmartins commentedon Nov 18, 2025
@puneetlath bump ^
puneetlath commentedon Nov 20, 2025
From what I can see, they are assigned two different Expensify Card virtual cards. One of them is from an Expensify Card feed that is tied to a workspace. And one of those is from an Expensify Card feed that is tied to a domain. So technically there are two different Expensify Card feeds, which is why they see two.
I could see that we could potentially make that more clear by putting the domain name after the feed name if it is a domain feed. But I also think this isn't really a common scenario that real customers have (at least right now). So my vote would be to just close the issue.
Thoughts on that?
luacmartins commentedon Nov 20, 2025
I'm cool with that!