Profile - Phone number duplicated when adding as a secondary contact

[kbecciv]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Issue found when executing PR #16804

Action Performed:

1. Launch the app and login
2. Open Settings -> Profile -> Contact method
3. Add your number and it should appear on the list

Expected Result:

Only one number must be displayed in the list

Actual Result:

Phone number gets duplicated and same number listed two times

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.3.2.3

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

Bug6025487_Recording__1932.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause- Internal Team

Slack conversation:

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~019cd0980077a37963
• Upwork Job ID: 1650516917226029056
• Last Price Increase: 2023-04-24

[MelvinBot]

Triggered auto assignment to @dylanexpensify (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

[mountiny]

@koko57 seems to be linked to your PR #16804 could you have a look into this

[koko57]

@koko57 seems to be linked to your PR #16804 could you have a look into this

Yeah, of course!

[koko57]

@mountiny looks like another change has introduced this issue - having this in v1.3.1-3

[mountiny]

Ok maybe @cristipaval or @Beamanator might know they are working on contact methods, sorry for the ping if not :D

[dylanexpensify]

Nice, should I proceed with checklist @mountiny !?

[mountiny]

I would wait for @cristipaval and @Beamanator to confirm before exporting this

[dylanexpensify]

@vit Horacek ***@***.***> why are you replying so late!?!? haahaha, ty!

…

On Mon, Apr 24, 2023 at 10:08 AM Vit Horacek ***@***.***> wrote: I would wait for @cristipaval <https://github.com/cristipaval> and @Beamanator <https://github.com/Beamanator> to confirm before exporting this — Reply to this email directly, view it on GitHub <#17722 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOKVCAE7RPI5JVSDH54VI7TXCY7H3ANCNFSM6AAAAAAXFX465U> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Beamanator]

Eyooo we just arrived in London so will check this out now :D