I am not sure if this is intended behavior, but I expected the keyboard to be attached to the native navigation container like this:
Expected (gif showing react-native-navigation with slow animations enabled)

Actual (gif showingreact-navigation with useScreens() with slow animations enabled)

"expo": "^32.0.0",
"react": "16.5.0",
"react-native": "https://github.com/expo/react-native/archive/sdk-32.0.0.tar.gz",
"react-native-screens": "^1.0.0-alpha.22",
"react-navigation": "^3.0.9"
Source: https://github.com/Thorbenandresen/react-native-screens-test
it's possible to do this but we did not implement it in react-navigation. cc @janicduplessis, can't remember exactly what the difficulties were
I鈥檓 not sure if it would be possible to do with rn-screens since we use viewcontrollers but I did try to animate the keyboard a while back and it did involve using a bunch of private apis and really nasty code.
Having some weird keyboard behavior when enabling Screens. Keyboard doesn't dismiss after navigating to another screen and back. Even on Keyboard.dismiss() call. It seems like without Screens keyboard is dismissed on every navigation.
Should I create a different issue?
On topic: animating keyboard with the screen would be great, feels more native.
@pyankoff - create a minimal repro and post a new issue
animating keyboard with screen - probably not going to do this but you're welcome to open a pr for it / a feature request on react-navigation
Most helpful comment
I鈥檓 not sure if it would be possible to do with rn-screens since we use viewcontrollers but I did try to animate the keyboard a while back and it did involve using a bunch of private apis and really nasty code.