-
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
Payments - Modal is not dismissed as soon as the payment method is Set as Default on the original device #15045
Comments
Triggered auto assignment to @puneetlath ( |
Bug0 Triage Checklist (Main S/O)
|
@kbecciv just to clarify, the bug is that you are getting an error when attempting to set the payment method as your default payment method, is that right? If so, I think this is a #passwordless issue and should be handled in https://github.com/Expensify/Expensify/issues/261738. @NikkiWines @johnmlee101 do you agree? |
No, the problem is that the modal is not dismissed as soon as the payment method is Set as Default on the original device |
This is PR #14869 |
@kbecciv I'm confused. In your video, the default payment method doesn't get set. There is an error when you try to do it. |
@puneetlath Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@puneetlath Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@puneetlath Huh... This is 4 days overdue. Who can take care of this? |
Ok I just tested this locally. The modal isn't dismissed when you do set default, but based on the test steps in the PR, that is expected. However, when I did delete the payment method, the modal was dismissed. So I think we're good here. Reopen if you disagree! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Issue found when executing PR #14869
Action Performed:
Expected Result:
Modal is dismissed as soon as the payment method is Set as Default on the original device
Actual Result:
Modal is not dismissed as soon as the payment method is Set as Default on the original device
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.2.69.2
Reproducible in staging?: Yes
Reproducible in production?: Yes
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
Notes/Photos/Videos: Any additional supporting documentation
Bug5932364_14869_mWeb__1_.mp4
Bug5932364_Screen_Recording_20230210_094044_Chrome.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: