[HOLD for payment 2023-07-14] [$1000] Web - Phone number is shown twice in the preview tooltip.

[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!

---

Action Performed:

1. Opened the website.
2. Hovered over the account without a name that contains a phone number.
3. Observed that the tooltip displays the contact details twice.

Expected Result:

The phone number should not be shown twice in the tooltip.

Actual Result:

The phone number is shown twice in the preview tooltip.

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.27-6

Reproducible in staging?: y

Reproducible in production?: y

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

Recording.5064.mp4

Expensify/Expensify Issue URL:

Issue reported by: @Tushu17

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

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~011baa54223aee0feb
• Upwork Job ID: 1671800200350584832
• Last Price Increase: 2023-06-22

[melvin-bot]

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

[melvin-bot]

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

[manjesh-yadav]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Web - Phone number is shown twice in the preview tooltip

What is the root cause of that problem?

We display two texts in the tooltip displayName and login

App/src/components/UserDetailsTooltip/index.js

Lines 26 to 32 in 0b7455f

	<Text style={[styles.mt2, styles.textMicroBold, styles.textReactionSenders, styles.textAlignCenter]}>
	{String(userDetails.displayName).trim() ? userDetails.displayName : ''}
	</Text>
	<Text style={[styles.textMicro, styles.fontColorReactionLabel]}>
	{String(userDetails.login || '').trim() && !_.isEqual(userDetails.login, userDetails.displayName) ? Str.removeSMSDomain(userDetails.login) : ''}
	</Text>

if login and displayName is the same we do not display the second text

we check this by this line of code

{String(userDetails.login || '').trim() && !_.isEqual(userDetails.login, userDetails.displayName) ? Str.removeSMSDomain(userDetails.login) : ''}

1. When user sign up with with there phone number we save the displayName same as the phone number and login id append with SMS domain "+phoneNumber@expensify.sms"
2. For the phone number case our condition failed to check login and displayName is same and we display same number twice

What changes do you think we should make in order to solve the problem?

While signup time, we have a method formatPhoneNumber in 'src/libs/LocalePhoneNumber.js' which is used to convert phone number to displayName

We can use the same method to check if login phone number is the same as the current displayName as (Why current? Because the user can update their displayName in the future)

if this return true if do not show the second text otherwise show

snippets:

const formatLoginIdAsDisplayName =  (login) => {
        if(!login){
            return null;
        }

        // If login type is not phone number return same login
        if(!Str.isSMSLogin(login)){
            return login;
        }
        // Remove SMS domain and format phone number as DisplayName
        return LocalePhoneNumber.formatPhoneNumber(Str.removeSMSDomain(login))
    }

//Now call this like

{String(userDetails.login || '').trim() && !_.isEqual(formatLoginIdAsDisplayName(userDetails.login), userDetails.displayName)? Str.removeSMSDomain(userDetails.login) : ''}

Result

display-name.mp4

What alternative solutions did you explore? (Optional)

If we do not want to show phone number in tooltip

from:

{String(userDetails.login || '').trim() && !_.isEqual(userDetails.login, userDetails.displayName) ? Str.removeSMSDomain(userDetails.login) : ''}

to like this:

{String(userDetails.login || '').trim() && !_.isEqual(userDetails.login, userDetails.displayName) && !Str.isSMSLogin(userDetails.login) ? Str.removeSMSDomain(userDetails.login) : ''}

[Tushu17]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Phone number is shown twice in tooltip on user with no name.

What is the root cause of that problem?

In the UserDetailsTooltip component, we are currently checking whether userDetails.login is equal to userDetails.displayName in order to determine if the user has a display name or not. This approach works correctly for accounts that use email as the login method. However, for phone number accounts, the userDetails.displayName string differs from the userDetails.login string.

App/src/components/UserDetailsTooltip/index.js

Line 31 in 0b7455f

{String(userDetails.login || '').trim() && !_.isEqual(userDetails.login, userDetails.displayName) ? Str.removeSMSDomain(userDetails.login) : ''}

What changes do you think we should make in order to solve the problem?

We can check if user has a empty userDetails.firstName and userDetails.lastName instead of checking userDetails.displayName

{String(userDetails.login).trim() && _.isEmpty(userDetails.firstName) && _.isEmpty(userDetails.lastName) ? '' : Str.removeSMSDomain(userDetails.login)}

What alternative solutions did you explore? (Optional)

Na

[conorpendergrast]

Reproduced on OSX desktop app too. Thanks!

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~011baa54223aee0feb

[melvin-bot]

Current assignee @conorpendergrast is eligible for the External assigner, not assigning anyone new.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @Santhosh-Sellavel (External)