Skip to content

[HOLD on #31771] [$500] Web -The user is unable to locate the 'Get Physical Card' button #31757

Closed

Description

@lanitochka17

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: 1.4.2.0
Reproducible in staging?: Y
Reproducible in production?: Y
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: Applause - Internal Team
Slack conversation:
Issue found when executing PR #28453

Action Performed:

  1. Go to staging.new.expensify.com
  2. Log in tester@applause.expensifail.com
  3. Go to Settings - Wallet
  4. Check for Get Physical Card button

Expected Result:

The user is able to locate the 'Get Physical Card' button

Actual Result:

The user is unable to locate the 'Get Physical Card' button

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • Windows: Chrome
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6287779_1700688218527.Recording__5509.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01a24984e3e44fd84d
  • Upwork Job ID: 1727438771200491520
  • Last Price Increase: 2023-11-29

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 22, 2023
  2. changed the title [-]Web -The user is unable to locate the 'Get Physical Card' button[/-] [+][$500] Web -The user is unable to locate the 'Get Physical Card' button[/+] on Nov 22, 2023
  3. melvin-bot commented on Nov 22, 2023

    @melvin-bot
  4. melvin-bot commented on Nov 22, 2023

    @melvin-bot

    Triggered auto assignment to @garrettmknight (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  5. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Nov 22, 2023
  6. melvin-bot commented on Nov 22, 2023

    @melvin-bot

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  7. melvin-bot commented on Nov 22, 2023

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @akinwale (External)

  8. shubham1206agra commented on Nov 23, 2023

    @shubham1206agra
    Contributor

    @lanitochka17 Can you share the Onyx data of the card? Otherwise, state values would be fine.

  9. grgia commented on Nov 23, 2023

    @grgia
    Contributor

    I think this issue may be linked to another bug where if a user has multiple expensify cards, all card pages link to the same card #31771

  10. grgia commented on Nov 23, 2023

    @grgia
    Contributor
  11. 32 remaining items

  12. garrettmknight commented on Feb 14, 2024

    @garrettmknight
    Contributor

    Still holding on #31771

  13. garrettmknight commented on Feb 23, 2024

    @garrettmknight
    Contributor

    Still holding on #31771

  14. garrettmknight commented on Mar 5, 2024

    @garrettmknight
    Contributor

    Still holding on #31771

  15. garrettmknight commented on Mar 14, 2024

    @garrettmknight
    Contributor

    Still holding on #31771

  16. garrettmknight commented on Mar 26, 2024

    @garrettmknight
    Contributor

    Closing since this will get solved by the held issue - it's a near duplicate.

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.ExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributorsMonthlyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions