-
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 - Auth CreateFund returned an error
appears when adding debit card
#32126
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 @srikarparsi ( |
Removing deploy blocker label as it's happening in production. |
@srikarparsi Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@srikarparsi 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
looked into the code, believe it's an error with stripe because of the status code, will make more progress tomorrow. |
@srikarparsi Eep! 4 days overdue now. Issues have feelings too... |
@srikarparsi Still overdue 6 days?! Let's take care of this! |
Had finals last week and this week but just finished them up. I'm OOO on Friday for graduation but will add this to my list of things to investigate tomorrow and will leave an update. |
@srikarparsi Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@srikarparsi Eep! 4 days overdue now. Issues have feelings too... |
Still looking into this, it's a Stripe error but I'm not able to find what changes could be causing this. I'll probably ask for help if I can't find an explanation tomorrow. |
@srikarparsi Eep! 4 days overdue now. Issues have feelings too... |
Working limited hours because of Christmas/New Year, will leave an update towards the beginning of next week |
Oh sorry to the missing ping. Yeah, we should ask them for a new token if it's expired. There should a GH created automatically every 3 months I think to request a new token. Let me find it |
These are the issues to request a new token https://github.com/Expensify/Expensify/issues?q=is%3Aissue+%22Rotate+Bancorp+RFT+API+Sandbox+token%22+, and this is the last one https://github.com/Expensify/Expensify/issues/296548. Could you look for the expiry date? The last time it was working was on Dec 21, 2023 but it probably already expired |
Got it, so I believe the next issue will be created on February 28th. So would next steps since the token already expired be to create one of these issues, assign it to myself, and rotate the token? |
Hey @marcochavezf! Friendly bump on the above question :) |
Yup, if we confirmed that token is expired then it will be time to contact Bancorp for another token. IIRC in another GH issue, Bancorp mentioned that another company/contact will be in charge of rotating the token. I think @deetergp has more info about it |
The next issue wasn't going to run until May, but it looks like we need it to run sooner. I retried the job and it generated the issue and assigned it to @francoisl here. Outside of that, the only real information I have is that dealing with Bancorp/Tabapay is a bit like pulling teeth. They are slow to respond and need to be bumped daily till you get what you need from them. 😬 |
Still seems to be failing. Logs here. The isDebitCard check is failing which means the Bancorp response doesn't have the "card" property. The Bancorp token seems to be rotated above but I'll check more on this tomorrow, maybe the response format might've changed for testing cards? |
This issue has not been updated in over 15 days. @srikarparsi eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
No update still |
This is no longer reproducible with this debit test card. Closing this out |
Issue is still reproducible Bug6526959_1719545907138.Desktop-Wallet-Debit-card-can-not-added.mp4 |
Hey, do you think you could try again with this card number: 4000056655665556. It's still working for me. |
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.1
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:
Issue found when executing PR #31133
Action Performed:
Expected Result:
The debit card is added without any errors
Actual Result:
Auth CreateFund returned an error
appearsWorkaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: