[HOLD #13623] New Room - A red dot appears with an error when selecting a new room and then canceling

[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. Launch the app
2. Log in with any account
3. Click menu Fab
4. Click New room
5. Click cancellation of new room creation

Expected Result:

The error with the red dot should not appear when selecting a new room and then canceling

Actual Result:

A red dot appears with an error when selecting a new room and then canceling

Workaround:

Unknown

Platforms:

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

• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.2.44.0

Reproducible in staging?: Yes

Reproducible in production?: Yes

Email or phone of affected tester (no customers):

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug5877919_new_room_red_dot.mp4

Expensify/Expensify Issue URL:

**Issue reported by:**Applause_- Internal Team

Slack conversation:

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~014f71f0d04a9efdcc
• Upwork Job ID: 1608151229178265600
• Last Price Increase: 2022-12-28

[melvin-bot]

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

[puneetlath]

I'm able to reproduce this on iOS, but not on Chrome.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~014f71f0d04a9efdcc

[melvin-bot]

Current assignee @puneetlath 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)

[melvin-bot]

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

[thesahindia]

@puneetlath, I think the root cause is same as #13024 and we should add this to the tracking issue

[puneetlath]

Sounds good. Thanks @thesahindia.

[puneetlath]

Still on hold.

[puneetlath]

Still on hold.

[puneetlath]

Still on hold.

[puneetlath]

Still on hold. Posted an idea in #13623 to try to keep the convo going.

[puneetlath]

Closing this in favor of #13623 since it'll be handled there.