Virtual keyboard dismisses when TextInput is focused

[anttilehtonen]

Environment

1. react-native -v:
   react-native-cli: 2.0.1
   react-native: 0.54.1

2. npm ls rnpm-plugin-windows:
   -- [email protected]

3. npm ls react-native-windows:
   [email protected]

4. node -v:
   v8.6.0

5. npm -v:
   5.3.0

6. yarn --version:

Then, specify:

• Target Platform: UWP

• Target Platform Version(s): 10.0.10586 UWP

• Target Device(s): Surface Pro Touchable Windows 10 Device

• Development Operating System: Windows

• Visual Studio Version: 2017

Steps to Reproduce

(Write your steps here:)

Preconditions: Device is in touchable mode so only virtual keyboard can be used.

1. Have 2 TextInputs in the view.
2. Click on TextInput Create ReactContentBaseMSModule Extensions #1.
3. Write some numbers to TextInput Create ReactContentBaseMSModule Extensions #1
4. Press Tab or Enter in Virtual Keyboard

Expected Behavior

Virtual keyboard remains open and focus moves to TextInput #2.

Actual Behavior

Focus moves to TextInput #2 but virtual keyboard dismisses.
User needs to press on TextInput #2 again to get keyboard up.
This does not reproduce in Android.

(Write what happened. Add screenshots!)

Reproducible Demo

This was reproduced with react-native init demo and having following code in render():
Added only TextInputs.

    <TextInput
      ref={ (ref) => this.input1 = ref }
      keyboardType="numeric"
      blurOnSubmit={false}
      onSubmitEditing={() => this.input2.focus()}
      style={{ width: '100%' }}
    />
    <TextInput
      ref={ (ref) => this.input2 = ref }
      keyboardType="numeric"
      blurOnSubmit={false}
      onSubmitEditing={() => this.input1.focus()}
      style={{ width: '100%' }}
    />

Demo where node modules and compiled binaries have been taken away.
textInputTest.zip

[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.