-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Web - Wallet - Cannot proceed with add bank account flow #32082
Comments
👋 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:
|
Triggered auto assignment to @marcaaron ( |
Checking this now. |
I think the wrong details are being used? We need to try with: First name: Alberta Tested on |
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 |
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:
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?
Screenshots/Videos
Add any screenshot/video evidence
Bug6292512_1701132405452.bandicam_2023-11-27_17-37-03-661.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: