[Android] double R in emulator brings keyboard after typing in TextInput

[greenais]

Environment

Environment:
OS: Windows 8.1
Node: 8.12.0
Yarn: 1.3.2
npm: 6.4.1
Watchman: Not Found
Xcode: N/A
Android Studio: Version 3.1.0.0 AI-173.4819257
Packages: (wanted => installed)
react: 16.6.1 => 16.6.1
react-native: 0.57.5 => 0.57.5

Description

After I typed in TextInput in any of my components reloading app in Android emulator with double R always brings up Android keyboard - even if component is inactive already (i.e. app navigated to another component). It can be hided by Android standard button, but this behaviour is quite irritating.

Do I miss something in handling InputText or this is any kind of bug/feature?

[react-native-bot]

It looks like you are using an older version of React Native. Please update to the latest release, v0.57 and verify if the issue still exists.

The "⏪Old Version" label will be removed automatically once you edit your original post with the results of running react-native info on a project using the latest release.

[greenais]

Any toughths on this?
It still happens with all the most recent versions of RN and emulator...

If it's expected and normal - just confirm please and feel free to close this issue to clean the stack

[Averybeast1234]

I am having the same issue

[bobber205]

Is there a good reason why Command + R isn't used instead of double tapping R?

[Averybeast1234]

Command R is a MacOs thing. Also it is not just the double tapping of R. Anytime a textInput is used and you render to another component that doesn't have one, any press of a letter key on hardware keyboard brings up the software keyboard even if there is not textinput that is being rendered or mounted.

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

[stale]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.