TextInput with multiline and fixed height shows inconsistent text positioning on initial render

[Jakes-Git-Hub]

Description

When using a TextInput with multiline={true}, fixed height, and textAlignVertical="top", the text positioning is inconsistent depending on navigation path. When a user first opens the app and navigates to a screen containing long text that overflows the TextInput, the text appears "squashed" towards the top with content cut off under the border. However, if the user navigates back to the home screen, opens a note with shorter content first, then returns to the long note, the text positioning displays correctly.

This appears to be a layout initialization timing issue where the TextInput doesn't properly calculate its content positioning on first render when dealing with overflow content.

Steps to reproduce

1. Clone the reproduction repository: git clone https://github.com/Jakes-Git-Hub/Multi-Line-Test.git
2. Install dependencies with npm install
3. Start the app with npx expo start
4. Open the app and immediately tap on either "Long Note Example" or "Another Overflow Note"
5. Observe that the text appears squashed towards the top with content cut off under the border
6. Navigate back to the home screen using the back button
7. Tap on the "Short" note (single word content)
8. Navigate back and tap on one of the long notes again
9. Observe that the text now displays correctly with proper positioning

Also if i go into another long note after initially opening a long note, the text positioning adjusts to a middle ground between squashed and what would be the text position if sequence was long note -> short note -> LN.

React Native Version

0.81.5

Affected Platforms

Runtime - iOS

Output of npx @react-native-community/cli info

System:
  OS: Windows 11 10.0.26100
  CPU: (12) x64 12th Gen Intel(R) Core(TM) i7-1255U
  Memory: 1.77 GB / 15.68 GB
Binaries:
  Node:
    version: 22.14.0
    path: C:\Program Files\nodejs\node.EXE
  Yarn: Not Found
  npm:
    version: 11.6.2
    path: C:\Program Files\nodejs\npm.CMD
  Watchman: Not Found
SDKs:
  Android SDK: Not Found
  Windows SDK: Not Found
IDEs:
  Android Studio: Not Found
  Visual Studio: Not Found
Languages:
  Java: Not Found
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 19.1.0
    wanted: 19.1.0
  react-native:
    installed: 0.81.5
    wanted: 0.81.5
  react-native-windows: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

Stacktrace or Logs

No crash occurs - this is a layout/rendering issue. The TextInput renders but with incorrect text positioning on initial load. No error messages or stack traces are generated.

MANDATORY Reproducer

https://github.com/Jakes-Git-Hub/Multi-Line-Test

Screenshots and Videos

Multi.Line.Bug.mp4

[krishx06]

Hey @Jakes-Git-Hub , I came across this issue and would like to take it up for investigation and a possible fix.
Could you please assign this issue to me?

I’ll start by setting up the environment and testing the provided reproduction repo to better understand the problem before proposing any changes.

Thanks!

[Jakes-Git-Hub]

@krishx06 I've just tried to assign you via the command as my Assignees option is greyed out for some reason, any idea why it is so?

Is there a triage bot we can use to assign the issue to you?

[krishx06]

@Jakes-Git-Hub I think only maintainers can assign

[krishx06]

Hi @Jakes-Git-Hub ,

I have been able to reproduce this issue in RNTester and have created a new example component named TextInputLayoutBugExample under
packages/rn-tester/js/examples/TextInputLayoutBug/TextInputLayoutBugExample.js.

This example demonstrates the inconsistent text positioning that occurs when using a multiline TextInput with a fixed height and textAlignVertical="top", as described in this issue.

I am preparing a pull request to add this example to RNTester to make it easier for others to test and debug this problem in future builds.

[Jakes-Git-Hub]

@krishx06 thanks for your help regarding this matter, I owe you an ice pop.

[react-native-bot]

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[react-native-bot]

This issue is stale because it has been open for 180 days with no activity. It will be closed in 7 days unless you comment on it or remove the "Stale" label.