-
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
Wallet - Unable to authenticate when connected Fidelity BA #46987
Comments
Triggered auto assignment to @tylerkaraszewski ( |
Triggered auto assignment to @JmillsExpensify ( |
👋 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:
|
I would guess this is on production already. Do other banks work? |
Plaid not supporting Fidelity is not a bug we need to fix. |
Agreed. For good measure, on staging we get this response. So yes, this is a Plaid issue and not us. 👍
|
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: v9.0.17-0
Reproducible in staging?: Y
Reproducible in production?: Unable to check
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4752874&group_by=runs:name&group_order=asc&group_id=-1
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-internal team
Action Performed:
Expected Result:
The authentication flow should be complete
Actual Result:
after step 6, returning from(closing) plaid modal it shows a message "unable to authenticate"
Workaround:
Unable to check
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: