Skip to content

Card - Tapping assign card in confirmation page directs to who needs a card page #62932

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: V9.1.53-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/6176122
Email or phone of affected tester (no customers): Applausetester hsbs@applause.ex
Issue reported by: Applause Internal Team
Device used: Redminote 10s android 13
App Component: Workspace Settings

Action Performed:

  1. Go to https://staging.new.expensify.com/home
  2. Go to workspace settings - enable company card
  3. Select united states - american express
  4. Enter credentials and complete the flow
  5. Tap assign a card and add a card
  6. Go to members - admin
  7. Tap new card - select a card and tap next
  8. Tap custom start date - next
  9. Tap assign card

Expected Result:

After tapping assign card in confirmation page user must direct to members page.

Actual Result:

After tapping assign card in confirmation page user directs to who needs a card instead members page.

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 May 28, 2025
  2. melvin-bot commented on May 28, 2025

    @melvin-bot

    Triggered auto assignment to @slafortune (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. melvin-bot commented on May 28, 2025

    @melvin-bot

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

  4. melvin-bot commented on May 28, 2025

    @melvin-bot

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

  5. github-actions commented on May 28, 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.
  6. BlameGPT commented on May 28, 2025

    @BlameGPT
  7. twilight2294 commented on May 28, 2025

    @twilight2294
    Contributor

    Not reproducible, @madmax330 can you test please, I think the API response was not successful for the tester, since they were only able to reproduce on one platform, either ways, i don't think so my PR caused the issue here as suggested by @Blame-GPT

  8. BlameGPT commented on May 28, 2025

    @BlameGPT
    Contributor

    Possible culprit PRs for this issue

  9. 8 remaining items

  10. slafortune commented on Jun 3, 2025

    @slafortune
    Contributor

    waiting on retests

  11. melvin-bot commented on Jun 9, 2025

    @melvin-bot

    @madmax330, @slafortune Huh... This is 4 days overdue. Who can take care of this?

  12. slafortune commented on Jun 10, 2025

    @slafortune
    Contributor

    updating to weekly for retest

  13. melvin-bot commented on Jun 11, 2025

    @melvin-bot

    @madmax330 @slafortune this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

  14. izarutskaya commented on Jun 24, 2025

    @izarutskaya

    Not reproduced

    Screenrecorder-2025-06-24-15-35-56-784.mp4
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.EngineeringWeeklyKSv2retest-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