UWP Soft Keyboard moves UI accordingly but doesn't affect Touchable Areas

[chukcha-wtf]

Environment

1. react-native -v: 0.55.1
2. npm ls rnpm-plugin-windows: 0.2.8
3. npm ls react-native-windows: 0.55.0-rc.0
4. node -v: v6.11.2
5. npm -v: 3.10.10

Then, specify:

• Target Platform: UWP

• Target Platform Version(s): 10.0.14393

• Target Device(s): Desktop (Microsoft Surface Pro 3)

• Development Operating System: Windows

• Visual Studio Version: Visual Studio 2017

• Build Configuration: Debug, DebugBundle, Release, ReleaseBundle

Steps to Reproduce

(Write your steps here:)

1. Create new ReactNative app
2. Create TextInput alongside with TouchableOpacity on the bottom of the screen.
3. Switch to TabletMode, focus on TextInput and wait till the Soft Keyboard appears on the screen.
4. TouchableOpacity stops responding to interactions.

Expected Behavior

(Write what you thought would happen.)

Actual Behavior

1. Create new ReactNative app
2. Create TextInput alongside with TouchableOpacity on the bottom of the screen.
3. Switch to TabletMode, focus on TextInput and wait till the Soft Keyboard appears on the screen.
4. TouchableOpacity should be responsive, user should be able to press on it w/out hiding keyboard.

The issue is related to Touchable Area's and Soft Keyboard on Windows.
When there is a Soft Keyboard triggered - the UI is correctly updated and moved to the top (not to cover Text Input) which is fine. But the touchable area's aren't moving with UI and might be covered by keyboard. So it's not possible to press anywhere in the app untill the Soft Keyboard will be hidden.

Example UI before keyboard appears:

Example UI after soft keyboard appears:

Reproducible Demo

https://github.com/chukcha-wtf/SoftKeyboardIssue

[ghost]

We are not investing in new features or lower priority bug fixes on vCurrent. The bulk of investment is now in vNext as we prepare to make that the default choice. If this issue is still relevant on the vNext implementation please open a vNext issue. If this issue is of significant severity for a vCurrent app and vNext is not an option, re-open with justification.