Skip to content

[$500] Bank account - Error flickers when trying to add bank account after deleting previous one #37271

Closed

Description

@izarutskaya

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: v1.4.44-0
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): applausetester+vd_web022624@applause.expensifail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal Team

Action Performed:

Pre-requisite: the user must be logged in and have created a workspace.

  1. Go to Workspace > Bank account.
  2. Using Connect online with Plaid, select Chase and complete the add BA flow.
  3. After BA has been added, disconnect the BA.
  4. Again, using Connect online with Plaid, select Regions and try to add the BA.
  5. On the account confirmation screen, click on "Confirm" button.
  6. Verify an error flickers and the user can not proceed with the flow.
  7. Exit the add BA modal.
  8. Go to Workspace > Bank account.
  9. Verify the new BA appears as connected.

Expected Result:

There should be any issue on the flow when trying to add the new BA.

Actual Result:

When trying to confirm the bank account, an error flickers and the user is not able to proceed with the flow. Also, if the user returns to the add BA modal, the new account seems to be connected.

Workaround:

Unknown

Platforms:

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

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

Screenshots/Videos

Bug6393621_1709011624372.bandicam_2024-02-26_20-58-47-575.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01bcfec6134c6b50b2
  • Upwork Job ID: 1762427912527470592
  • Last Price Increase: 2024-02-27

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    ExternalAdded to denote the issue can be worked on by a contributor
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 27, 2024
  2. changed the title [-]Bank account - Error flickers when trying to add bank account after deleting previous one[/-] [+][$500] Bank account - Error flickers when trying to add bank account after deleting previous one[/+] on Feb 27, 2024
  3. melvin-bot commented on Feb 27, 2024

    @melvin-bot
  4. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Feb 27, 2024
  5. melvin-bot commented on Feb 27, 2024

    @melvin-bot

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

  6. melvin-bot commented on Feb 27, 2024

    @melvin-bot

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

  7. github-actions commented on Feb 27, 2024

    @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.
  8. 29 remaining items

  9. mvtglobally commented on Mar 5, 2024

    @mvtglobally

    Issue is reproducible during KI retests.

  10. removed
    retest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause
    on Mar 5, 2024
  11. self-assigned this
    on Mar 5, 2024
  12. nkuoch commented on Mar 5, 2024

    @nkuoch
    Contributor

    Will take a look myself, to see if I see any BE or FE issue.

  13. added
    InternalRequires API changes or must be handled by Expensify staff
    and removed
    ExternalAdded to denote the issue can be worked on by a contributor
    Help WantedApply this label when an issue is open to proposals by contributors
    on Mar 5, 2024
  14. melvin-bot commented on Mar 5, 2024

    @melvin-bot

    Current assignee @abdulrahuman5196 is eligible for the Internal assigner, not assigning anyone new.

  15. nkuoch commented on Mar 5, 2024

    @nkuoch
    Contributor

    This will be a BE PR, no need for contributor plus

  16. slafortune commented on Mar 22, 2024

    @slafortune
    Contributor

    @nkuoch no payment is due on this one, right? Can this be closed now?

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.EngineeringInternalRequires API changes or must be handled by Expensify staffReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions