Skip to content

Payments - Unable to add bank fully verified account #3953

Closed

Description

@isagoico

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Payments - Unable to add bank fully verified account

Action Performed:

  1. Log in to e.cash
  2. Navigate to /bank-account/new
  3. Click on Log in to bank account
  4. Enter the test credentials

Expected Result:

User can proceed to add the bank account.

Actual Result:

User is redirected back to the add bank account options (log in or manually). JS console shows this errror:

image

Platform

Where is this issue confirmed?

Web ✔️
iOS
Android
Desktop App
Mobile Web (Android only)

Is it reproducible in production? : Unable to verify (test credentials don't work in Prod)

Build version: 1.0.76-1

Notes/Images/Video

image


Found while executing #3776

Activity

  1. MelvinBot commented on Jul 9, 2021

    @MelvinBot
    Contributor

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

  2. NikkiWines commented on Jul 9, 2021

    @NikkiWines
    Contributor

    Hmm, I think it's expected that we wouldn't set up a bank account due to there being existing owners. Looks like we have a TODO for it to be updated with better error in the UI as well

    // Show warning if another account already set up this bank account and promote share
    if (response.existingOwners) {
        // @TODO Show better error in UI about existing owners
        console.error('Cannot set up withdrawal account due to existing owners');
       return;
    }

    @marcaaron looks like this is your TODO, do you know if we have a plan/open issue for this already? If not, maybe we can tag design and finalize what we want the UI to look like so that this would be ready for a contributor to pick up.

  3. removed their assignment
    on Jul 9, 2021
  4. marcaaron commented on Jul 10, 2021

    @marcaaron
    Contributor
  5. NikkiWines commented on Jul 12, 2021

    @NikkiWines
    Contributor

    Great! Looks like @jasperhuangg has a PR up to updated that already 🎉 I'll link this issue to that PR.

  6. MelvinBot commented on Oct 11, 2021

    @MelvinBot
    Contributor

    This issue has not been updated in over 15 days. eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  7. MelvinBot commented on Dec 7, 2021

    @MelvinBot
    Contributor

    @isagoico, this Monthly task hasn't been acted upon in 6 weeks; closing.

    If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.

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