Skip to content

[$250] mweb-cards-Minor visual glitch on navigating back from concierge to cards page #61668

Closed

Description

@mitarachim

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.42-0
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/6068249
Email or phone of affected tester (no customers): Slottwo1 sivappa2@gmail.com
Issue reported by: Applause Internal Team
Device used: Redminote note 10s android 13
App Component: Workspace Settings

Action Performed:

  1. Go to https://staging.new.expensify.com/home
  2. Go to workspace settings
  3. Tap company card - add card - american express - american express corporate card
  4. Complete the flow
  5. Tap concierge link
  6. Tap device back button

Expected Result:

Tapping device back button from concierge page, minor visual glitches (green) must not be seen in cards page briefly.

Actual Result:

Tapping device back button from concierge page, minor visual glitches (green) can be seen in cards page briefly. In production behaviour no green minor glitches.

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

Bug6825294_1746689289225.Screenrecorder-2025-05-08-12-52-38-762.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021920420725439306402
  • Upwork Job ID: 1920420725439306402
  • Last Price Increase: 2025-06-19
Issue OwnerCurrent Issue Owner: @parasharrajat

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on May 8, 2025
  2. melvin-bot commented on May 8, 2025

    @melvin-bot

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

  3. melvin-bot commented on May 8, 2025

    @melvin-bot

    Triggered auto assignment to @dylanexpensify (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.

  4. melvin-bot commented on May 8, 2025

    @melvin-bot

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

  5. github-actions commented on May 8, 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. removed
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on May 8, 2025
  7. 44 remaining items

  8. melvin-bot commented on Jun 12, 2025

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  9. mvtglobally commented on Jun 16, 2025

    @mvtglobally

    Issue not reproducible during KI retests. (First week)

  10. melvin-bot commented on Jun 16, 2025

    @melvin-bot

    @parasharrajat Eep! 4 days overdue now. Issues have feelings too...

  11. melvin-bot commented on Jun 18, 2025

    @melvin-bot

    @parasharrajat 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

  12. parasharrajat commented on Jun 18, 2025

    @parasharrajat
    Member
  13. melvin-bot commented on Jun 19, 2025

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  14. mvtglobally commented on Jun 21, 2025

    @mvtglobally

    Issue not reproducible during KI retests. (Second week)

  15. melvin-bot commented on Jun 23, 2025

    @melvin-bot

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

  16. melvin-bot commented on Jun 24, 2025

    @melvin-bot

    @parasharrajat Eep! 4 days overdue now. Issues have feelings too...

  17. parasharrajat commented on Jun 24, 2025

    @parasharrajat
    Member

    Knock Knock @dylanexpensify, let's close this.

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

Metadata

Metadata

Labels

DailyKSv2ExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributors

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions