Error message ''A room with this name already exist'' isn't displayed after type the same name for room the Room Name input

[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. Click "New Room" in the global create menu
2. Type test_room_name into the room name input and select a workspace. Click "Create Room".
3. Type test_room_name into the Room Name input and Click "Create Room".

Expected Result:

Verify that the A room with this name already exists error message displays (in real-time as you finish typing test_room_name).

Actual Result:

Error "the A room with this name already exists" message isn't displays.

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Web
• iOS
• Android
• Desktop App
• Mobile Web

**Version Number:1.1.20-0
**Reproducible in staging?:Yes
**Reproducible in production?:No
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Video
Expensify/Expensify Issue URL:
**Issue was found when executing:**#6314
Slack conversation:

View all open jobs on GitHub

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

[MelvinBot]

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

[mountiny]

@TomatoToaster This is a regression from the New Room PR. I do not think this must be a deploy blocker as it does not break anything, but it would be good to investigate. The tester has copied the string name into the text input field, which is different way than what I could see on the videos in the PR where it was typed, so not sure if that could be the reason.

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

[mountiny]

PR up and ready