[Android] TextInput secureTextEntry doesn't work if it have a keyboardType prop with values 'email-address' or 'phone-pad'

[samuelpismel]

• [ ✓ ] 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

Environment:
OS: Linux 4.4
Node: 8.11.3
Yarn: 1.9.2
npm: 6.3.0
Watchman: Not Found
Xcode: N/A
Android Studio: Not Found

Packages: (wanted => installed)
react: 16.3.1 => 16.3.1
react-native: https://github.com/expo/react-native/archive/sdk-29.0.0.tar.gz => 0.55.4

Description

[Android Only]

If you have an keyboardType prop with values 'email-address' or 'phone-pad' in your TextInput the secureTextEntry doesn't work and the input shows its value as a normal input (not like an password input).

Reproducible Demo

Snack full example: https://snack.expo.io/HkqrRfqS7

<TextInput
  secureTextEntry
  keyboardType="email-address"
/>

<TextInput
  secureTextEntry
  keyboardType="phone-pad"
/>

[isis1234]

omg that useful for me!! thank you very much!

[lubnaski]

Hello thanks for sharing.

But do you know why we can't paste from clipboard when the textinput is secure text? I tried your code on expo and the working one can't paste from clipboard while the one that didn't work can paste from clipboard.

[insideMan15]

Hi, thank you for your answer. I have met the same problems.

After resolving it, I think for the password input the keyboardType="default" is better than others in android.

[slorber]

can confirm, setting keyboardType default seems to fix this :o

[buchidiai]

wow thanks just saved me from 3 hrs of debugging

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