[Due for payment 2025-08-05] [$250] iOS - Chat - Expand button does not appear in composer when entering multiline text

[jponikarchuk]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.1.71-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/6354433
Email or phone of affected tester (no customers): fischer9966+062425eee@gmail.com
Issue reported by: Applause Internal Team
Device used: iPhone 16 Pro / 18.5
App Component: Chat Report View

Action Performed:

1. Open iOS App
2. Login with any account
3. Go to any chat
4. Enter multiline text more then 3 lines into Composer

Expected Result:

Expand button appears in composer when entering multiline text more then 3 lines long

Actual Result:

Expand button does not appear in composer when entering multiline text more then 3 lines long. Expand button appears if user re-enter the chat without sending this message.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021937954205581340877
• Upwork Job ID: 1937954205581340877
• Last Price Increase: 2025-07-02
• Automatic offers:
• linhvovan29546 | Contributor | 107981180

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @muttmuure

[melvin-bot]

Triggered auto assignment to @muttmuure (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

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

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

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

[Eskalifer1]

Proposal

Please re-state the problem that we are trying to solve in this issue.

iOS - Chat - Expand button does not appear in composer when entering multiline text

What is the root cause of that problem?

The cause of the problem is the behavior of iOS with onContentSizeChange. On IOS, when enableScroll !== false, onContentSizeChange may not work because of the internal implementation of UITextView on IOS.

What changes do you think we should make in order to solve the problem?

To do this, we need to change the function:

App/src/pages/home/report/ReportActionCompose/ComposerWithSuggestions/ComposerWithSuggestions.tsx

Lines 775 to 785 in 67e472c

	const updateIsFullComposerAvailable = useCallback(
	(e: NativeSyntheticEvent<TextInputContentSizeChangeEventData>) => {
	const paddingTopAndBottom = (containerComposeStyles.paddingVertical as number) * 2;
	const inputHeight = e.nativeEvent.contentSize.height;
	const totalHeight = inputHeight + paddingTopAndBottom;
	const isFullComposerAvailable = totalHeight >= CONST.COMPOSER.FULL_COMPOSER_MIN_HEIGHT;
	setIsFullComposerAvailable?.(isFullComposerAvailable);
	},
	[setIsFullComposerAvailable, containerComposeStyles],
	);

Take out the internal logic as follows:

    const computeIsFullComposerAvailable = useCallback(
        (inputHeight: number) => {
            const paddingTopAndBottom = (containerComposeStyles.paddingVertical as number) * 2;
            const totalHeight = inputHeight + paddingTopAndBottom;
            const isFullComposerAvailable = totalHeight >= CONST.COMPOSER.FULL_COMPOSER_MIN_HEIGHT;
            setIsFullComposerAvailable?.(isFullComposerAvailable);
        },
        [containerComposeStyles, setIsFullComposerAvailable],
    );

    const updateIsFullComposerAvailable = useCallback(
        (e: NativeSyntheticEvent<TextInputContentSizeChangeEventData>) => {
            const inputHeight = e.nativeEvent.contentSize.height;
            computeIsFullComposerAvailable(inputHeight);
        },
        [computeIsFullComposerAvailable],
    );

Add a check for IOS and call this function in onLayout:

    const onLayout = useCallback(
        (e: LayoutChangeEvent) => {
            onLayoutProps?.(e);
            const composerLayoutHeight = e.nativeEvent.layout.height;
            if (composerHeight === composerLayoutHeight) {
                return;
            }
            setComposerHeight(composerLayoutHeight);

            if (isIOSNative) {
                textInputRef.current?.measure?.((x, y, width, height, pageX, pageY) => {
                    const inputHeight = height - (containerComposeStyles.paddingVertical as number) * 2;
                    computeIsFullComposerAvailable(inputHeight);
                });
            }
        },
        [composerHeight, onLayoutProps],
    );

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

None

What alternative solutions did you explore? (Optional)

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[blimpich]

Looking into this. I don't think this is worth blocking deploy on, but I'll see if I can find the offending PR before demoting.