Repository navigation
[Android][TextInput] Bug when combine secureTextEntry + keyboardType props #26799
Description
React Native version:
System:
OS: Linux 4.15 Linux Mint 19.1 (Tessa)
CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
Memory: 5.34 GB / 15.51 GB
Shell: 2.7.1 - /usr/bin/fish
Binaries:
Node: 10.16.3 - /usr/bin/node
Yarn: 1.17.3 - ~/.yarn/bin/yarn
npm: 6.11.3 - /usr/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.2 => 0.61.2
npmGlobalPackages:
create-react-native-web-app: 0.1.14
react-native-cli: 2.0.1
react-native-create-library: 3.1.2
Steps To Reproduce
- Just use
secureTextEntry+keyboardType
<TextInput secureTextEntry keyboardType="email-address"/>
<TextInput secureTextEntry keyboardType="phone-pad"/>
- Now you will see that on Android when
keyboardTypeisemail-addressorphone-padvalue visible for users.
Describe what you expected to happen:
Should work the same as iOS
Snack & code example:
https://snack.expo.io/@retyui/2793f1
Activity
[-][Android][TextInput] Combine props bug secureTextEntry + keyboardType[/-][+][Android][TextInput] Bug when combine secureTextEntry + keyboardType props[/+]stale commentedon Jan 8, 2020
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 commentedon Apr 7, 2020
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 commentedon Jul 6, 2020
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.
8 remaining items
github-actions commentedon May 19, 2023
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.
retyui commentedon May 19, 2023
any progress?
NishitTibicle commentedon Jul 24, 2023
Come on guys ? this is not working in android do something for it
github-actions commentedon Jul 24, 2023
github-actions commentedon Jan 22, 2024
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.
shubhamguptadream11 commentedon Sep 9, 2024
Hi @retyui,
After looking into the issue, it appears that the inability to mask text input when using keyboardType="phone-pad" with secureTextEntry is the default behavior on Android. The
InputType.TYPE_CLASS_PHONEdoes not support secure text masking [here], which is why the text remains visible. This is the expected behavior on Android and not specific to React Native.