Input inside of Portal duplicates text

[crutchcorn]

Current behaviour

When a react-native TextInput is inside of a Portal (even if as a descendant, say, inside nested Views inside of a Modal ), when the user types, it will (inconsistently) duplicate the existing text in the input box

There doesn't seem to be a correlation between how much the user types. In my app (a non-minimal repro that I won't link), it seems to be nearly every 2-3 characters, but the minimal repro that I WILL link happens significantly more infrequently

I have only confirmed this behavior on Android, have not tested on iOS.

Expected behaviour

Text inputs in Portal should not duplicate text incorrectly

Code sample

https://github.com/crutchcorn/rn-paper-portal-bug-repro

Screenshots (if applicable)

What have you tried

• Upgrading react-native
• Upgrading react-native-paper
• Creating minimal repro
• Confirmed this happens on both emulator and physical device

Your Environment

software	version
ios or android	android v11
react-native	0.64.2
react-native-paper	4.9.1
node	12.16.1
npm or yarn	yarn 1.22.5
expo sdk	n/a

[github-actions]

Couldn't find version numbers for the following packages in the issue:

• react-native-vector-icons
• npm
• expo

Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3.

The versions mentioned in the issue for the following packages differ from the latest versions on npm:

• yarn (found: 1.22.5, latest: 1.22.10)

Can you verify that the issue still exists after upgrading to the latest versions of these packages?

[lukutism]

Up, faced same issue. :)

[alexandreerick]

Same issue here.

[andordavoti]

Same issue here, facing this after upgrading from React Native v0.62.2 to v0.63.0

[lukewalczak]

Is that issue still valid? Wondering whether the reported bug is specific to the library or react-native in general.

[petrometro]

As of RN 0.67.2 and RNP 4.11.2, I ran into this problem when I had a TextInput inside a Modal (which was inside a Portal), testing on a Samsung Galaxy Tab.
The solution of setting autoCorrect={false} on the TextInput worked for me.

[JoshuaSkootsky]

this is a really weird bug and nothing has prepared me for this.