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