You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-12-04] [Due for payment 2025-11-26] Domain Cards Not Displayed in Workspace Company Cards Page Despite API Returning Them #73380
Version Number: Reproducible in staging?: Needs Reproduction Reproducible in production?: Needs Reproduction If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by:@puneetlath Slack conversation (hyperlinked to channel name): #Migrate
Action Performed:
Preconditions:
User A has domain-issued Expensify Cards.
Preferred workspace is assigned to User A’s domain cards.
User A has access to the workspace.
Log in as User A (who has assigned domain cards)
Navigate to the Workspace where the cards are configured
Go to Workspace
Open Company Cards tab
Inspect API responses for returned card data
Expected Result:
All domain cards assigned to the user and linked to the workspace should be displayed in the Company Cards UI if returned in the API response.
Actual Result:
The API correctly returns the company card details for the user.
But no cards are displayed in the UI under the Company Cards section — the list appears empty.
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:
changed the title [-][Due for payment 2025-11-26] Domain Cards Not Displayed in Workspace Company Cards Page Despite API Returning Them[/-][+][Due for payment 2025-12-04] [Due for payment 2025-11-26] Domain Cards Not Displayed in Workspace Company Cards Page Despite API Returning Them[/+]on Nov 27, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.64-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@hungvu193@heyjennahay / @stephanieelliott The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: Improvement to the current feed name logic.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal
Precondition:
User A has domain-issued Expensify Cards.
Preferred workspace is assigned to User A’s domain cards.
User A has access to the workspace.
Inspect API responses for returned card data
Test:
Log in as User A (who has assigned domain cards)
Navigate to the Workspace where the cards are configured
Go to Workspace
Open Company Cards tab
Verify that all domain cards assigned to the user and linked to the workspace should be displayed in the Company Cards UI if returned in the API response.
Activity
melvin-bot commentedon Oct 23, 2025
Triggered auto assignment to @stephanieelliott (
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.MelvinBot commentedon Oct 23, 2025
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
melvin-bot commentedon Oct 28, 2025
@stephanieelliott Huh... This is 4 days overdue. Who can take care of this?
stephanieelliott commentedon Oct 30, 2025
I was also unable to repro, seeing as no C+ have stepped forward I've posted to see if we can get an agency dev on it: https://expensify.slack.com/archives/C03UK30EA1Z/p1761866538165669
melvin-bot commentedon Oct 30, 2025
@stephanieelliott Still overdue 6 days?! Let's take care of this!
VickyStash commentedon Oct 31, 2025
Hi, I'm Viktoryia from Callstack - expert contributor group - and I would like to work on this issue!
40 remaining items
melvin-bot commentedon Nov 26, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
[-][Due for payment 2025-11-26] Domain Cards Not Displayed in Workspace Company Cards Page Despite API Returning Them[/-][+][Due for payment 2025-12-04] [Due for payment 2025-11-26] Domain Cards Not Displayed in Workspace Company Cards Page Despite API Returning Them[/+]melvin-bot commentedon Nov 27, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.64-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-12-04. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Nov 27, 2025
@hungvu193 @heyjennahay / @stephanieelliott The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
hungvu193 commentedon Dec 4, 2025
BugZero Checklist:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: Improvement to the current feed name logic.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal
Precondition:
Inspect API responses for returned card data
Test:
Do we agree 👍 or 👎
melvin-bot commentedon Dec 4, 2025
Payment Summary
Upwork Job
BugZero Checklist (@heyjennahay)
heyjennahay commentedon Dec 5, 2025
Regression test requested https://github.com/Expensify/Expensify/issues/574954
Payment summary:
Confirmed no Upwork job/contract/pffer to close
garrettmknight commentedon Dec 7, 2025
$250 approved for @hungvu193
heyjennahay commentedon Dec 8, 2025
Looks like we're done here. Thanks everyone for your work