-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Bank account - The user is not seeing the connection flow view when selecting 'Connect online with Plaid #32596
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 @hayata-suenaga ( |
Production: Recording.5641.mp4 |
This is not a deploy blocker. |
confirming that Plaid flow doesn't work on the staging environment. After confirmation, we can close this issue. |
I think this is expected. closing the issue |
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.9.0
Reproducible in staging?: Y
Reproducible in production?: N
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:
Action Performed:
Expected Result:
The user is seeing the connection flow view when selecting 'Connect online with Plaid like in production
Actual Result:
The user is not seeing the connection flow view when selecting 'Connect online with Plaid
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6303731_1701900185183.Recording__5647.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: