Closed kevinksullivan closed 1 week ago
Triggered auto assignment to @jliexpensify (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.
Hey, I'm Agata from Callstack, I've been working on this feature, I can take a look 😊
Thanks, assigned you!
ok, so it's still the problem with the bankAccount objects being different in AcceptACHContractForBankAccount
and OpenPaymentsPage
- after we're adding a bank account we don't have the additionalData
object within the bankAccount - we have a flatter structure where plaidAccountID
is the property of the accountData
bankAccount object not additionalData
. So it works ok when we remove additionalData
and we check for accountData?.plaidAccountID
instead of accountData?.additionalData?.plaidAccountID
.
AcceptACHContractForBankAccount
But, when we go to Wallet page response from OpenPaymentsPage
is different and it has additionalData
property and SET method for Onyx, so it overwrites the bankAccount data and when we go back to the Expensify Cards page this fix doesn't work anymore - without the fix it works ok (the button is not shown).
OpenPaymentsPage
So we need to get the bankAccount object the very same from all the requests to either check for additionalData or not.
cc @mountiny @MariaHCD
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 plaidAccountID
prop to accountData in AcceptACHContractForBankAccount? Alternatively should we just have the FE look for the prop in both accountData?.plaidAccountID
and accountData?.additionalData?.plaidAccountID
?
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 https://github.com/Expensify/App/issues/47944
This hit prod two weeks ago, can we close it?
I don't believe there are any payments, @mountiny feel free to close if this is fixed.
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