[$1000] Chat - Send button is not enabled if only 1 character is typed after sending another message

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

---

Action Performed:

Pre-requisite: user must be logged in and in any chat

1. Type and send any message
2. Type a new message with only 1 character

Expected Result:

The send button should be enabled after typing 1 character

Actual Result:

User must have to type more than 1 character for the send button to be enabled

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

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

Notes/Photos/Videos: Any additional supporting documentation

Bug6155681_Esbp2194_1_.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/~010168816ae3accfb6
• Upwork Job ID: 1688437010257268736
• Last Price Increase: 2023-08-07

[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 @techievivek (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[hungvu193]

Feel like this is issue with our current react native version when multiline is enable. The commit caused this issue:
facebook/react-native@a804c0f

We can apply this diff (AudiusProject/audius-client#3622) to resolve this issue or waiting for our upstream to upgrade to latest RN version.

[techievivek]

@hungvu193

Feel like this is issue with our current react native version when multiline is enable.

Did we enable multiline recently?

[hungvu193]

@hungvu193

Feel like this is issue with our current react native version when multiline is enable.

Did we enable multiline recently?

Yep. you can try to set it to false in our Composer and this issue will be solved.

App/src/pages/home/report/ReportActionCompose.js

Lines 1170 to 1174 in 8e608db

	<Composer
	checkComposerVisibility={() => this.checkComposerVisibility()}
	autoFocus={this.shouldAutoFocus}
	multiline
	ref={this.setTextInputRef}

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~010168816ae3accfb6

[melvin-bot]

Triggered auto assignment to @sonialiap (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @mollfpr (External)

[techievivek]

@hungvu193 Okk, then using the patch sounds good to me.

[pradeepmdk]

already discussed here both are same issue #24147

[techievivek]

@pradeepmdk ohh, thanks. We are discussing this internally if we should update the RN version or can we just patch-fix this.

[pradeepmdk]

Thanks for the update @techievivek

[MonilBhavsar]

Closing, considering a dupe of #24147