Android TV: Keyboard automatically open when pressing numeric key in specific conditions

Description

Keyboard automatically open when pressing numeric key (KEYCODE_1, … ) after removing an InputText from the View on AndroidTV (not tested on ios, but not sure it makes sens as there is no key number on apple TV)

React Native version:

0.66.3-3

Steps To Reproduce

Run following sample. This is just a dummy InputText which is removed from main View onSubmit. Once you end typing text, the view disappear. At that point, if you press numerical key on remote control, the keyboard is automatically opened.

As a complementary test, if you initialize show state to false and input numerical Keycode, the issue is not reproduced.

Reproduced on multiple Androidtv devices and on emulator. Keycode can be simulate with following adb command: ‘adb shell input keyevent KEYCODE_1’

Expected Results

The keyboard should not show at that point.

code example:

Sample project : https://github.com/freeboub/React-Native-tvos-demo/tree/sample_keyboard_issue

code sample code:

` import React, {useRef} from ‘react’; import {View, TextInput, LogBox} from ‘react-native’;

const TVEventHandlerView = () => { const [show, setShow] = React.useState(true);

const firstRef = useRef();

return ( <> {show && ( <> <TextInput ref={firstRef} defaultValue={‘hello’} showSoftInputOnFocus={true} autoFocus={true} editable={true} onChangeText={() => { console.log(‘onTextChange’); }} onSubmitEditing={() => { console.log(‘onSubmitEditing’); setShow(false); }} placeholder={‘Search…’} /> </> )} </> ); };

export default function App() { return ( <View style={{flex: 1}}> <TVEventHandlerView /> </View> ); } ` Additionnal interesting informations:

• If I add a TouchableWithoutFeedback after the InputText the issue is not reproduce (I think focus correctly moves to the TouchableWithoutFeedback)
• If I launch google voice assistant the incorrect behavior disappear.

[douglowder]

Thanks for the detailed information and repro, and for creating the new issue for the core repo. I’ll see what the RN core Android developers think about what the issue really is, before picking this up.

[freeboub]

Here are some addtionnal informations:

• to workaround the issue I tried to implement by own InputText component (I can share it if needed), but the same issue is reproduced with a custom component, so I think we can asume the issue is not directly linked to EditText management in react-native. It’s really looks like a low level issue. Maybe a reference leak …
• I found an ‘ugly’ workaround which is working. When a TextInput is blured or unmounted, I launch an empty transparent activty. This activity just call finish onResume… Then the activity stack is correctly cleared and keyboard doesn’t take the focus instead of our app. I causes a very small freeze in UI, but It is better than this issue.