[TextInput] Blur event is broken in v0.57.6

[ahce]

• Review the documentation: https://facebook.github.io/react-native
• Search for existing issues: https://github.com/facebook/react-native/issues
• Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment

React Native Environment Info:
    System:
      OS: Windows 10
      CPU: (4) x64 Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz
      Memory: 4.29 GB / 11.87 GB
    Binaries:
      Yarn: 1.12.3 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
      npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD
    IDEs:
      Android Studio: Version  3.1.0.0 AI-173.4907809
    npmPackages:
      react: 16.6.1 => 16.6.1
      react-native: 0.57.6 => 0.57.6

Description

The input is not focused after the blur event with the done button.
Blur event was broken with this commit,

Reproducible Demo

1. Focus the input
2. Press the done button in keyboard
3. Try focus the input again

[radeno]

@gazoudoudou can you check that please?

[radko93]

Happens only on Android for me (I will label it like that), if anyone can reproduce on iOS please write it here.

[kelset]

Hey @ahce thanks for the report, since it's a fairly big issue I'll revert that commit and create a new release asap.

[Minishlink]

@kelset Shouldn't we fix the underlying issue? It seems wrong that this "double blur" is needed on Android and not on iOS (and that it is needed at all)

[kelset]

@Minishlink absolutely, the issue should get a proper fix: but that needs to be a PR to master and fix it 'once and for all'.

This revert & new release is to simply prevent people from facing it in 0.57.patch - now that we are aware of the fact of that commit being broken, I'll leave this issue open so that we can properly fix it.

@ahce let me know if 0.57.7 works fine for you now (I just created a test project and was able to repro, and updating to 0.57.7 fixed this)

[ahce]

@kelset works fine in 0.57.7, Thanks!

[sahrens]

FYI, @RSNara has a fix incoming to master.

[sahrens]

Fix is to revert #22156

[radko93]

@sahrens so there's no better fix for that? IMO at least on iOS we should not call it twice.

[sahrens]

We're reverting for now to be safe. Could potentially add an iOS check if it's causing problems.

[kelset]

Closing since this issue has actually being fixed by the revert.