[$500] Room - @expensify.sms suffix appears after invitation & disappears after opening user avatar

[lanitochka17]

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

---

Version Number: 1.4.31-2
Reproducible in staging?: Y
Reproducible in production?: N
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
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Action Performed:

1. Go to a room
2. Click on the room header > Members > Invite
3. Invite via phone number
4. Return to the main chat
5. Click on the phone number in the invite notification
6. Note that it shows @expensify.sms
7. Click on the avatar
8. Close the avatar

Expected Result:

@expensify.sms should remain (behavior on production)

Actual Result:

@expensify.sms suffix disappears after opening user avatar

Workaround:

Unknown

Platforms:

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

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6353531_1706119428365.20240124_194713.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01bcbbe2d08d76f86e
• Upwork Job ID: 1752445825076850688
• Last Price Increase: 2024-03-19
• Automatic offers:
• dukenv0307 | Contributor | 0

[melvin-bot]

Triggered auto assignment to @tylerkaraszewski (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[thienlnam]

Not sure if this was an intentional update or not. But doesn't seem to need to be a blocker

[melvin-bot]

@tylerkaraszewski Huh... This is 4 days overdue. Who can take care of this?

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01bcbbe2d08d76f86e