Payment - One of payment methods becomes a default automatically

[kbecciv]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Action Performed:

Preconditions: user hasn't any or has only 1 payment method

1. Go to URL https://staging.new.expensify.com/
2. Login with any account
3. Go to Settings -> Payment
4. Add a second payment method (if you already have one) or add 2 payment methods (if you don't already have one)

Expected Result:

None of the payment methods become default automatically

Actual Result:

One of payment methods becomes a default automatically

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.2.94.0

Reproducible in staging?: Yes

Reproducible in production?: N/a

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

Bug6005525_Record_2023-04-04-13-00-23.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1680742028391019

View all open jobs on GitHub

[MelvinBot]

Triggered auto assignment to @arielgreen (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[MelvinBot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[arielgreen]

Raised discussion about expected behavior here.

[arielgreen]

bumped discussion

[arielgreen]

I'm going to go ahead and close this; no response to discussion and I don't actually think this is a bug.