-
Notifications
You must be signed in to change notification settings - Fork 24.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We need better handling of multiple inputs with secureTextEntry on iOS 12+ #25603
Comments
Thanks for submitting your issue. Can you take another look at your description and make sure the issue template has been filled in its entirety? 👉 Click here if you want to take another look at the Bug Report issue template. |
You can use https://facebook.github.io/react-native/docs/textinput#textcontenttype to hint the OS about the type of input |
That’s the thing, on iOS 12 that prop and the autoCorrect one don’t work in regards to not showing the email suggestions on the 2nd secureTextEntry input. |
Strange, maybe it is a bug in UIKit, not sure if we can do anything about it :( |
Yeah, in the app I'm working on currently this problem appears even if I have just two inputs: email and password. If I move focus from email to password and back, the password suggestion tooltip appears when email field is focused, and email suggestion tooltip appears when password is focused. Or no tooltip at all. I'm using 0.60.4. |
I have the same issue :( |
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. |
Still an issue. iOS 13.2 |
@hramos what does 'Needs author feedback' tag mean? |
Fixed the label - this issue does not make use of the template, and it's missing necessary information. @hbarylskyi feel free to open a new issue that makes use of the issue template, as this one might get closed if it's not edited soon. |
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. |
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. |
So before iOS 12 we were able to have multiple inputs with
secureTextEntry
and the auto suggestions were correct or not there unless specified in props. It seems now with iOS 12 and above that if you render 3 inputs: 1 without secureTextEntry first, then the other 2 with secureTextEntry last, that no matter what, iOS 12> will always think the input before the first secureTextEntry input is an email field and will show email suggestions. iOS will also think that the second secureTextEntry input is also an email field and will show email suggestions. There's no way to hide it except for only have 1 secureTextEntry input. Even then the suggestions are determined by iOS and props are almost useless. This wasn't the case with iOS 11.Reproduction:
https://snack.expo.io/BkxZysBZB
As you can see, when the iOS version is less than 12, this works as intended. We can have multiple inputs with the secureTextEntry prop and it will not show email suggestions on them.
Now, run that same snack on a physical device on the expo app that is on iOS 12+
Ignoring the autofill feature, you can see that by default, iOS will show auto suggestions for email on the second secureTextEntry input.
My questions to the react-native core team is: How do you handle multiple secureTextEntry inputs in iOS 12? It seems that we have to put up with the wrong auto suggestions types and just deal with it.
(Pictures for clarity)
iOS 11 first input:
iOS 12 first input:
iOS 11 third input:
iOS 12 third input:
The text was updated successfully, but these errors were encountered: