You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Android it is possible to get a Keyboard with letters and numbers visible at the same time through the property textVisiblePassword
In Flutter, we use a TextField with the property obscureText: true to get the password behavior, so there is no TextInputType relative to the password field, so we can not achieve the same effect when using the textVisiblePassword property
Support has been added with the PR referenced above. Make sure you're on the master channel or you have the next version to be released after 1.8.2. Then you can do this:
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
justinmc commentedon Apr 29, 2019
Sounds like this would be a good addition to Flutter to me. We would need to add support for InputType.TYPE_TEXT_VARIATION_VISIBLE_PASSWORD into TextInputPlugin.java in the engine, and then tie it through to TextInputType in the framework. Should be a straightforward change.
niktses commentedon Jul 22, 2019
Is there any update on this? I really need it to release my app
Add support for Android's visible password input type (#9999)
justinmc commentedon Jul 23, 2019
@niktses Support was added in the engine in flutter-team-archive/engine#9999, and this PR will add the input type to the framework when it's merged: #36695
niktses commentedon Jul 23, 2019
Thanks a lot
justinmc commentedon Jul 29, 2019
Support has been added with the PR referenced above. Make sure you're on the master channel or you have the next version to be released after 1.8.2. Then you can do this:
Thanks for requesting this!
github-actions commentedon Aug 29, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.