Skip to content

[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

Closed

Description

@m-natarajan

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:
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.
  1. Log in as User A (who has assigned domain cards)
  2. Navigate to the Workspace where the cards are configured
  3. Go to Workspace
  4. Open Company Cards tab
  5. 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:
  • 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

The screenshot for the issue is in OP

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @heyjennahay / @stephanieelliott
Issue OwnerCurrent Issue Owner: @heyjennahay / @stephanieelliott

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 23, 2025
  2. melvin-bot commented on Oct 23, 2025

    @melvin-bot

    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.

  3. MelvinBot commented on Oct 23, 2025

    @MelvinBot
    Contributor

    This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

  4. melvin-bot commented on Oct 28, 2025

    @melvin-bot

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

  5. added
    retest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause
    on Oct 30, 2025
  6. stephanieelliott commented on Oct 30, 2025

    @stephanieelliott
    Contributor

    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

  7. melvin-bot commented on Oct 30, 2025

    @melvin-bot

    @stephanieelliott Still overdue 6 days?! Let's take care of this!

  8. VickyStash commented on Oct 31, 2025

    @VickyStash
    Contributor

    Hi, I'm Viktoryia from Callstack - expert contributor group - and I would like to work on this issue!

  9. 40 remaining items

  10. melvin-bot commented on Nov 26, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  11. 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
  12. melvin-bot commented on Nov 27, 2025

    @melvin-bot

    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:

    • @hungvu193 requires payment through NewDot Manual Requests
    • @VickyStash does not require payment (Contractor)
  13. melvin-bot commented on Nov 27, 2025

    @melvin-bot

    @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]

  14. hungvu193 commented on Dec 4, 2025

    @hungvu193
    Contributor

    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:

    • 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:

    1. Log in as User A (who has assigned domain cards)
    2. Navigate to the Workspace where the cards are configured
    3. Go to Workspace
    4. Open Company Cards tab
    5. 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.

    Do we agree 👍 or 👎

  15. melvin-bot commented on Dec 4, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    • Reviewer: @hungvu193 owed $250 via NewDot
    • Contributor: @VickyStash is from an agency-contributor and not due payment

    BugZero Checklist (@heyjennahay)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  16. heyjennahay commented on Dec 5, 2025

    @heyjennahay
    Contributor

    Regression test requested https://github.com/Expensify/Expensify/issues/574954

    Payment summary:

    • @hungvu193 please request $250 payment via NewDot

    Confirmed no Upwork job/contract/pffer to close

  17. garrettmknight commented on Dec 7, 2025

    @garrettmknight
    Contributor

    $250 approved for @hungvu193

  18. heyjennahay commented on Dec 8, 2025

    @heyjennahay
    Contributor

    Looks like we're done here. Thanks everyone for your work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.Needs ReproductionReproducible steps neededWeeklyKSv2retest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions