Contact/Phone numbers ( NOT emails ) are flagged as violation while mentioning in public rooms

[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. Go to '+" -> new room
2. Type in room name -> add workspace
3. (IMPORTANT STEP) make room as public
4. Now on room page, on room chat, type '@' and mention some contact number ( WORKS WELL WITH EMAILS)
   for eg . i did mentioned @+9779866****** phone number
5. Notice that it is flagged automatically

Expected Result:

Contact numbers should not be flagged as a violation of rule, as in real we might need to mention some user ( which has signed up using phone number)

Actual Result:

Contact numbers are flagged as violation while mentioning in public rooms

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

Reproducible in staging?: n/a

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

Screen.Recording.2023-06-24.at.8.35.20.PM.mov

Expensify/Expensify Issue URL:

Issue reported by: @ashimsharma10

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

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0108e1fd1f5b114d4b
• Upwork Job ID: 1673384510798495744
• Last Price Increase: 2023-06-26

[OSBotify]

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

[melvin-bot]

Triggered auto assignment to @stitesExpensify (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[ashimsharma10]

@stitesExpensify

[thienlnam]

Stites is OOO, will take this up

[thienlnam]

Ah, this would be related to the spam prompt and should be happening on staging and production. Going to remove the blocker and add as an example to https://github.com/Expensify/Expensify/issues/292287

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~0108e1fd1f5b114d4b

[melvin-bot]

Triggered auto assignment to Contributor Plus for review of internal employee PR - @rushatgabhane (Internal)

[thienlnam]

Haven't updated this yet - planning with rest of AgentZero updates

[thienlnam]

Same as above

[thienlnam]

Haven't gotten around to this

[thienlnam]

Same - hoping to this week

[melvin-bot]

@thienlnam Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

@thienlnam 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[thienlnam]

Have an internal PR up

[thienlnam]

This should be live now - checking if this is resolved

[thienlnam]

Looks like this is resolved now - just to pay out bug reporter

[melvin-bot]

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

[thienlnam]

cc @tjferriss

I resolved this bug internally, could we get a payout for the bug reporter?
Issue reported by: @ashimsharma10

[tjferriss]

@ashimsharma10 I just sent you an offer via Upworks https://www.upwork.com/jobs/~0158147e2a0ebeea58

[ashimsharma10]

@tjferriss Have accepted.

[tjferriss]

The payment has been made.