Skip to content

Workspace - Expensify Card tab is present on the duplicated workspace when duplicated offline #69062

Closed

Description

@jponikarchuk

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.98-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from TestRail: #67412
Email or phone of affected tester (no customers): applausetester+140823kh2h1@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

  • Workspace is set up with Expensify card and has assigned at least one card to any member.
  1. Go to staging.new.expensify.com
  2. Go to workspace list.
  3. Go offline.
  4. Click 3-dot menu on the workspace that has Expensify Card.
  5. Click Duplicate Workspace.
  6. Click Next.
  7. Click Continue.
  8. Go to the duplicated workspace > Expensify Card.

Expected Result:

Expensify Card tab should not be present on the duplicated workspace.

Actual Result:

Expensify Card tab is present on the duplicated workspace when duplicated offline and it shows all the assigned cards.
After returning online, Expensify Card tab disappears.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Aug 22, 2025
  2. melvin-bot commented on Aug 22, 2025

    @melvin-bot

    Triggered auto assignment to @sonialiap (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. github-actions commented on Aug 22, 2025

    @github-actions
    Contributor

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

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  4. melvin-bot commented on Aug 22, 2025

    @melvin-bot

    Triggered auto assignment to @roryabraham (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  5. melvin-bot commented on Aug 22, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  6. mountiny commented on Aug 23, 2025

    @mountiny
    Contributor

    cc @narefyev91 for visibility #69055

  7. mountiny commented on Aug 23, 2025

    @mountiny
    Contributor

    The feature PR was reverted so I think we can close this issue and @narefyev91 can add it to PR v2

  8. narefyev91 commented on Aug 26, 2025

    @narefyev91
    Contributor

    Based on the design doc:
    "Expensify Card - We will not show this option, but if it is enabled via “More features” it will be enabled in the new workspace with no feed copied" - i will fix offline mode.
    But when user goes back online - Expensify card menu item should be available - we need to check on BE side - why "areExpensifyCardsEnabled" - set to false - if workspace which we try to duplicate has areExpensifyCardsEnabled = true

  9. mountiny commented on Aug 26, 2025

    @mountiny
    Contributor

    Raised a PR with a fix

  10. melvin-bot commented on Sep 3, 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. melvin-bot commented on Sep 3, 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.

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions