Skip to content

Web - Wallet - Cannot proceed with add bank account flow #32082

Closed

Description

@kbecciv

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.4.0
Reproducible in staging?: y
Reproducible in production?: unable to check production
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 #31050

Action Performed:

  1. Go to staging.new.expensify.com
  2. Create new account.
  3. Navigate to https://staging.new.expensify.com/send/new/enable-payments
  4. Fill the form with following data: First name: Alberta, Last name: Bobbeth, SSN: 3333, Any other information for the rest of the fields.
  5. Tap on "Save & continue".s

Expected Result:

The user should be able to proceed with the testing credentials.

Actual Result:

An error appears and the user is not able to proceed.

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

Add any screenshot/video evidence

Bug6292512_1701132405452.bandicam_2023-11-27_17-37-03-661.mp4

View all open jobs on GitHub

Activity

  1. github-actions commented on Nov 28, 2023

    @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.
  2. melvin-bot commented on Nov 28, 2023

    @melvin-bot

    Triggered auto assignment to @marcaaron (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  3. marcaaron commented on Nov 28, 2023

    @marcaaron
    Contributor

    Checking this now.

  4. marcaaron commented on Nov 28, 2023

    @marcaaron
    Contributor

    I think the wrong details are being used? We need to try with:

    First name: Alberta
    Last name: Charleson

    Tested on main and it works fine. I will try on staging just to be sure...

  5. marcaaron commented on Nov 28, 2023

    @marcaaron
    Contributor

    Works on staging as well. Going to close/remove the blocker as I think this is just a mistake on the tester's part.

    2023-11-28_11-52-12.mp4
  6. removed their assignment
    on Nov 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions