New contact method

[cristipaval]

Details

cc @Beamanator

Fixed Issues

$ #15318

Tests and QA Steps

1. Sign in and go to Profile -> Contact Method
2. Add new contact method which isn't claimed by another user
3. Verify that you are redirected to Contact Methods and the newly added contact method is in the list
4. Validate it and verify that the green indicator goes away
5. Add a new contact method which is added already to another account
6. Verify that you are redirected to the contact methods list and the newly added one has a red indicator with an error
7. Verify that you can successfully remove the contact methods added in the steps above

• Verify that no errors appear in the JS console

Offline tests

1. Go to Contact Methods on deviceA
2. Sign in with the same account and go to contact methods on deviceB
3. Turn off the internet on deviceA
4. Add a new contact method
5. Verify that you are redirected back to Contact Methods and the newly added contact method is in a pending action
6. Turn on the internet on deviceA
7. Verify that the newly added contact method is not greyed out anymore and you can click and validate it
8. Verify on deviceB that the new contact method is listed in Contact Methods page

Screen.Recording.2023-03-30.at.13.42.04.mov

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • The only data being stored in the state is data necessary for rendering and nothing else
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
• I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

web.mov

Mobile Web - Chrome

mobile.chrome.mov

Mobile Web - Safari

mobile.safari.mov

Desktop

desktop.mov

iOS

ios.native.mov

Android

Screen.Recording.2023-03-29.at.18.33.12.mov

[cristipaval]

Not overdue, waiting for a reverted PR to be merged back into main

[marcaaron]

Can I do anything to help unblock you here @cristipaval ?

[cristipaval]

@marcaaron this is ready for a new review.

[marcaaron]

Looks great! Nice work. Gonna merge this so we can keep charging!

addressed I think @marcochavezf let us know if there are additional comments

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[OSBotify]

🚀 Deployed to staging by https://github.com/marcaaron in version: 1.2.99-0 🚀

platform	result
🤖 android 🤖	failure ❌
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	failure ❌
🕸 web 🕸	success ✅

[OSBotify]

🚀 Deployed to production by https://github.com/francoisl in version: 1.2.99-6 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

[parasharrajat]

Heads up! There is a regression #17343 from this PR because deleteContactMethod expects two parameters to clear the local error optimistically.

[Santhosh-Sellavel]

We didn't trim the login value, which caused this bug here

[s77rt]

This PR caused a bug #18207. The submitted login should have the sms domain appended in case of a phone number (we could have achieved this using addSMSDomainIfPhoneNumber).

[sobitneupane]

Hello everyone, vertical margin was not added with DotIndicatorMessage causing this issue.

Issue: #17847
Title: No margin above Remove button in Contact method Detail screen

Steps To Reproduce:

1. Go to settings -> Profile -> Contact methods
2. Click New contact method -> Add any email which is already on Expensify.
3. Click Add button
4. Go to detail screen of that same email
5. You can notice that there is no margin above Remove button

[eVoloshchak]

👋 This has caused a small regression in #18003
Since this is an email/phone TextInput, it should've had the email keyboard type

[Beamanator]

Not lowercasing the contactMethod caused issues when people started testing mixed-case contact methods - #19080