Closed izarutskaya closed 2 months ago
Triggered auto assignment to @anmurali (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.
@anmurali Huh... This is 4 days overdue. Who can take care of this?
@anmurali 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
@anmurali 10 days overdue. Is anyone even seeing these? Hello?
We are going to remove debit cards temporarily as a payment device, so let's close this issue for now.
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.12-0 Reproducible in staging?: Y Reproducible in production?: Y If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/runs/view/22984&group_by=cases:section_id&group_order=asc&group_id=229064 Email or phone of affected tester (no customers): bellicoignacio+93@gmail.com Logs: https://stackoverflow.com/c/expensify/questions/4856 Issue reported by: Applause-Internal team
Action Performed:
Expected Result:
After completing all the fields with valid data, the user should be able to save the new debit card.
Actual Result:
After completing all the fields with valid data and tapping on the "Save" button, the user receives an "Make sure you've entered a valid debit card" error message and is unable to save the new debit card. The card number used was taken from the "Sandbox Test Cards" link
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
https://github.com/user-attachments/assets/47785a02-ae18-466d-9d45-51a7628eb23b
View all open jobs on GitHub