Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expensify card - I'm not redirected to Issue New Card flow after adding a BA #48152

Closed
4 of 6 tasks
izarutskaya opened this issue Aug 28, 2024 · 9 comments
Closed
4 of 6 tasks
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Engineering

Comments

@izarutskaya
Copy link

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: 9.0.25-4
Reproducible in staging?: Y
Reproducible in production?: N
Founding when validation PR #47844
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

  1. Log in with a new expensifail account
  2. Create a workspace
  3. Navigate to Workspace settings - More features
  4. Enable "Expensify Card"
  5. Navigate to Workspace settings - Expensify Card
  6. Click on the "Issue new card" button
  7. Add Regions bank with Plaid

Expected Result:

I should be redirected to the "Issue New Card" flow.

Actual Result:

I'm not redirected to the "Issue New Card" flow after adding a bank account. I have to click on the "Issue new card" button again.

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

Bug6584345_1724777504871.bug1.mp4

View all open jobs on GitHub

@izarutskaya izarutskaya added DeployBlockerCash This issue or pull request should block deployment Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. DeployBlocker Indicates it should block deploying the API labels Aug 28, 2024
Copy link

melvin-bot bot commented Aug 28, 2024

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

Copy link

melvin-bot bot commented Aug 28, 2024

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

Copy link
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.

@izarutskaya
Copy link
Author

I am unsure and add both blocker labels. Please delete if it's need. Thank you

Production - no "Issue new card" button

Screenshot (639)

@mountiny
Copy link
Contributor

looking

@mountiny mountiny assigned mountiny and unassigned NikkiWines Aug 28, 2024
@mountiny mountiny added Daily KSv2 and removed DeployBlockerCash This issue or pull request should block deployment Hourly KSv2 DeployBlocker Indicates it should block deploying the API labels Aug 28, 2024
@mountiny
Copy link
Contributor

This is not a blocker as the cards are behindbeta

@mountiny
Copy link
Contributor

@mountiny
Copy link
Contributor

From looking at the video this seems like expected behaviour to me. the admin first needs to add the VBBA and only then they start the issue new card flow choosing the settlement account first.

@DylanDylann
Copy link
Contributor

Agree with @mountiny

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Engineering
Projects
None yet
Development

No branches or pull requests

5 participants