Skip to content

Staging/Dev: Adding VBA using plaid bounces the user to manual step of adding Routing/Account number #6940

Closed

Description

@aldo-expensify

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


Action Performed:

  1. Create new dot account
  2. Create Workspace
  3. Add VBA account using plaid:
    • Bank: Chase
    • User: user_good
    • Password: pass_good

Expected Result:

After choosing the saving account, it should take the user to the "Company information" step

Actual Result:

User is taking to the "Connect bank account" step where he can manually input Routing and Account number

Screen.Recording.2021-12-29.at.4.13.34.PM.mov

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Input manually the Routing/Account numbers

Platform:

Where is this issue occurring?

  • Web
  • iOS
  • Android
  • Desktop App
  • Mobile Web

Version Number:
Reproducible in staging?:
Reproducible in production?:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    AutoAssignerTriageAuto assign issues for triage to an available triage team member
    on Dec 29, 2021
  2. MelvinBot commented on Dec 29, 2021

    @MelvinBot
    Contributor

    Triggered auto assignment to @mateocole (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

  3. removed
    AutoAssignerTriageAuto assign issues for triage to an available triage team member
    on Dec 29, 2021
  4. OSBotify commented on Dec 29, 2021

    @OSBotify
    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.
  5. MelvinBot commented on Dec 29, 2021

    @MelvinBot
    Contributor

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

  6. aldo-expensify commented on Dec 29, 2021

    @aldo-expensify
    ContributorAuthor

    Oh, I think that this may be intended behaviour now: #6851, but not 100% because in the PR they mention OAuth, which I'm not sure if it is the case here.

  7. aldo-expensify commented on Dec 30, 2021

    @aldo-expensify
    ContributorAuthor

    Closing this as this is intended behaviour now.

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

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions