Android 11 supports password providers securely sending autofill information to be displayed on the keyboard instead of a clunky dropdown menu. Bitwarden should require minimal changes to get that working.
Related topics + references
We are definitely looking forward to leveraging native autofill options for Mobile
Would love to see this! I’ve noticed that there are certain apps that don’t detect bitwarden autofill, or misbehave by forcing a reload and loosing the values after the autofill is done. Perhaps this would fix those issues and make it easier to use overall.
It would be really awesome to see this at Android 11 launch in October.
Echoing that I too would love to see this alongside the public android 11 release
Android 11 has been released:
Is there a plan for this?
Yep! It’s a fairly high priority item.
Any update, or ETA, or perhaps a link to the issue being tracked somewhere else that one could follow? Or is there any way that folks might be able to help?
It’s in motion currently! We’re working through some items with Xamarin but it’s definitely underway!
Still a work in progress, but moving along! Lots of interesting technical changes (with Android and Xamarin) that were needed for this to work, so it’s taking just a bit longer.
Is there a beta to help with testing?
It’s not in beta just yet, but it should be in our Beta path in Google Play once it’s working initially.
Looks like there’s been a PR submitted:
So hopefully pushed to beta soon
So, this showed up in beta sometime recently and in general I really like it, but some percentage of my apps don’t support the native autofill capability and so I have to keep both the autofill service and accessibility service settings on. In apps that DO support autofill, this results in the “Autofill with Bitwarden/Go to my vault” banner being displayed on top of the password field where I would have to click in order for the keyboard to come up. This makes it difficult to get at the nice new keyboard buttons to fill in the login. I tried turning the accessibility service off and that makes things much cleaner, but of course when I use an app that doesn’t support autofill I’m hosed. Is there any way to suppress the banner generated by the accessibility service when the app in question supports autofill? Or at least, don’t place the banner in a spot that makes it difficult to bring up the keyboard?
Looks like this is now live - unfortunately Swiftkey (my preferred Android keyboard) haven’t launched their support yet, but when I trialled Gboard it seemed to work fine with it.
Just cleaning up some open topics - this is available