-
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
Wallet - Error for invalid IBAN should be "Invalid IBAN" instead of "400 invalid IBAN" #54751
Comments
Triggered auto assignment to @cristipaval ( |
Triggered auto assignment to @MitchExpensify ( |
💬 A slack conversation has been started in #expensify-open-source |
👋 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:
|
Minor issue that needs a backend fix. |
@IuliiaHerets I don't see a 400 error in the video, am I missing something? |
@MitchExpensify Can you please check the last 5 seconds of the video? |
@cristipaval, @MitchExpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
^Backend fix is ready for review |
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: 9.0.80-1
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): applausetester+394034@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.0 / Chrome
App Component: User Settings
Action Performed:
Expected Result:
The error message should display "Invalid IBAN".
Actual Result:
The error message displays "400 Invalid IBAN".
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6705009_1735810703012.20250102_173501.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: