Chat - When sending a message to a new user, it is repeated and remains in the compose box

[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. Open the App
2. Log in any account
3. Click New chat
4. Open conversation with new user
5. Send message this new user.

Expected Result:

Compose box must be empty after sending a message to a new user

Actual Result:

When sending a message to a new user, it is repeated and remains in the compose box

Workaround:

Unknown

Platform:

Where is this issue occurring?

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

Version Number: 1.2.11.0

Reproducible in staging?: Yes

Reproducible in production?: No

Email or phone of affected tester (no customers): any

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

Notes/Photos/Videos: Any additional supporting documentation

Bug5759178_Recording__1443.mp4

Bug5759178_compose_box_1.10.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

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.

[melvin-bot]

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

[melvin-bot]

⚠️ Looks like this issue was linked to a possible regression on PRODUCTION here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a production regression has occurred a Root Cause Analysis is required. Please follow the instructions here.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[AndrewGable]

Removing deploy blocker because fire room was created.

[mallenexpensify]

@AndrewGable , it appears we have multiple 'message stays in compose box' GH issues. was this one fixed? What's fireroom you mentioned above?

[AndrewGable]

Fireroom: https://expensify.slack.com/archives/C04549KMEN6

This one was fixed via #11552

[mallenexpensify]

Dropped this into the #fireroom

This issue of text disappearing when typing after sending a chat is still happening to me on staging Version 1.2.12-0 . Is it supposed to be fixed with #11552 and #11526 ?

2022-10-06_08-03-35.mp4

[mallenexpensify]

^ nvm, separate, and equally annoying bug, #11490

[mallenexpensify]

@youssef-lr since you're assigned to this issue, can you please do an RCA? The template is here. If you know the offending PR that caused the bug, the employee or C+ who worked on that PR should do the regression. Reopening til the RCA is done.

I've added the high-level deets to the RCA Sheet

[youssef-lr]

Server-side fix has been deployed to staging and I can confirm I can longer reproduce this.

[mvtglobally]

Issue not reproducible during KI retests. (First week)

[mvtglobally]

Issue not reproducible during KI retests. (Second week)

[youssef-lr]

This has been fixed. Closing!