Android - Composer - Expand button does not appear when reopening chat with long draft

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.19-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: N/A
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause - Internal Team

Action Performed:

1. Launch New Expensify app
2. Go to chat
3. Enter text long enough until expand button appears
4. Return to LHN
5. Open the chat in Step 3

Expected Result:

Expand button will appear next to the composer

Actual Result:

Expand button does not appear next to the composer until anything is typed in the composer

Workaround:

Unknown

Platforms:

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

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6569731_1723462871743.c.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @rlinoz (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[github-actions]

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

[rlinoz]

Not a backend issue.

[rlinoz]

I think this is related to #46796, but I don't think it is worth blocking on this.

cc: @hannojg

[rlinoz]

Removing the deploy blocker label because this is an edge case and typing in the composer shows up the expand button again.

[hannojg]

Okay, will work on a fix today!

[hannojg]

@kirillzyusko is helping with this ticket!

[kirillzyusko]

Yep, feel free to assign it to me!

[kirillzyusko]

I prepared a fix #47449

But since we updated RN to the latest version (0.75) earlier - this bug is not reproducible anymore:

Screen.Recording.2024-08-29.at.18.42.09.mov

@rlinoz @hannojg @lanitochka17 what are the next steps then? Should we re-test this issue on latest main and if it's not reproducible, then close the issue and close the PR?

[hannojg]

Should we re-test this issue on latest main and if it's not reproducible, then close the issue and close the PR?

Yes, that sounds right!

[rlinoz]

Yep, just tested it in the latest app version and it works fine, let's close this one.

Thanks!