-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
[Workspace Feeds] Showing the request a limit increase button, despite the settlement account being set up with plaid. #48943
Comments
Triggered auto assignment to @jliexpensify ( |
Hey, I'm Agata from Callstack, I've been working on this feature, I can take a look 😊 |
Thanks, assigned you! |
Hmmm, this discrepancy sounds similar to https://github.com/Expensify/Auth/pull/12043 Seems like we need to properly clean up the formats such that they are not different across commands cc: @nkuoch For now, can we add the |
yeah lets fix this in App for now https://expensify.slack.com/archives/C036QM0SLJK/p1726058812587419?thread_ts=1725898727.642509&cid=C036QM0SLJK and then clean the data along with #47944 |
we're showing the button to request a limit increase, despite the settlement account being set up with a plaid connection.
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Reproducible in 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): kevinksullivan88+workspacefeed@gmail.com
Slack conversation: https://expensify.slack.com/archives/C036QM0SLJK/p1725976051148139
Action Performed:
Expected Result:
The
Request limit increase
button should not be shown. From the doc:Actual Result:
The
Request limit increase
button is shown even though the bank account is connected to plaid.Platforms:
Screenshots/Videos
Add any screenshot/video evidence
Onyx data:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: