You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading to new architecture + hermes, I've encountered a bug where the renderContent component changing height (while keyboard is open) causes the component to stop being rendered. This happens on both simulator and the real device. Android doesn't have an issue.
In my situation a TextInput that is set with multiline is causing it, but any sort of dynamic height change causes it to stop being rendered.
Type Ms with the soft-keyboard until the text box would wrap
Note it jumps to behind the keyboard after being resized.
Expected behavior
The TextInput box should grow vertically but keep its original position (above the keyboard) when it grows in height.
Actual behavior
The TextInput box drops below the keyboard when it changes height.
More Info
Using react-navigation library, which I have seen some reports of issues with. Given its popularity though it would be great if it could still work, since this is the dominant library for building custom keyboards + accessories.
Description
After upgrading to new architecture + hermes, I've encountered a bug where the
renderContent
component changing height (while keyboard is open) causes the component to stop being rendered. This happens on both simulator and the real device. Android doesn't have an issue.In my situation a TextInput that is set with
multiline
is causing it, but any sort of dynamic height change causes it to stop being rendered.I am using react-navigation in this project.
Related to
Steps to reproduce
Minimal reproduction repo: https://github.com/zzorba/keyboard-bug
Expected behavior
The TextInput box should grow vertically but keep its original position (above the keyboard) when it grows in height.
Actual behavior
The TextInput box drops below the keyboard when it changes height.
More Info
Using react-navigation library, which I have seen some reports of issues with. Given its popularity though it would be great if it could still work, since this is the dominant library for building custom keyboards + accessories.
Code snippet
Link to repro file
Environment
Affected platforms
The text was updated successfully, but these errors were encountered: