Android has had an autofill feature for password managers for years now, but it’s broken and needs to be fixed.

47 points

Yeah, it’s really a mystery to me how this can be so inconsistent across providers. With one app I have to click a separate button/dropdown-thingy and another fills the username and password in directly.

permalink
report
reply
26 points

And on top of that Google’s own password manager which I had deactivated managed to weasel itself into the foreground on my kid’s phone. It was a pain to deactivate it again.

permalink
report
parent
reply
7 points

Never had that happen actually

permalink
report
parent
reply
13 points

No idea how it happened. I think when my wife created an account for something on there it asked to save it. And since then it intercepted every password request.

permalink
report
parent
reply
9 points

For me I just have to click on the entry, if the KeePass DB is unlocked. Otherwise I click on the “KeePass2Android” entry, it opens the app, I unlock it and it either autofills or I just then finally click the entry.

permalink
report
parent
reply
7 points

As it should be. But for some inane reason it works differently for other apps.

permalink
report
parent
reply
31 points

I dunno, I use Bitwarden and Firefox on Android so pretty none mainstream and don’t have any of the issues this clown does. Seems like a click bait article for the sake of it.

permalink
report
reply
28 points

Bitwarden works well in every app and browser I’ve tried.

permalink
report
parent
reply
18 points

My banking apps lock screens consistently aren’t recognized by Bitwarden Android.

Some websites/apps only show the email field at first, then add the password field afterwards. This also sometimes makes it not being detected as a login form.

Sometimes a password field is detected only on the first filling in (which is annoying when choosing the wrong entry).

On desktop it’s great, but I really don’t know why some apps have to do custom login screens.

permalink
report
parent
reply
Deleted by creator
permalink
report
parent
reply
1 point

That banking apps are annoying isnt news :p

permalink
report
parent
reply
10 points

That’s because Bitwarden used various methods to enable auto-fill in places where the native auto-fill capability of Android doesn’t work. See https://bitwarden.com/help/auto-fill-android/ for an explanation.

permalink
report
parent
reply
9 points

Same setup, and its largely fine, but about 5-10% of the time bitwarden/keyboard will fail to show the password auto complete buttons, and I’ll have to copy paste manually, or restart Firefox. Really annoying, albeit rare.

permalink
report
parent
reply
7 points

Agreed… depending on Google to implement or fix very specific features is just shouting into the void. Use a trusted 3rd party app like Bitwarden, as you mentioned

permalink
report
parent
reply
4 points

+1 from me as well. I almost never have issues with Bitwarden. And when I do its usually in apps that don’t allow autofill in a normalish way. So I’m not sure thays really Google’s or Bitwarden’s fault, but the app developers…

permalink
report
parent
reply
3 points

Yeah, I had this sort of experience back with LastPass, but Bitwarden works beautifully for me.

There’s a potentially valid criticism if that occurs because iOS’s mechanism is robust to poorly implemented password managers and Android’s isn’t, but that’s also not the criticism being provided here.

permalink
report
parent
reply
1 point

Mixed experiences beyond firefox with bitwarden. But they are usually minuscule.

permalink
report
parent
reply
19 points

Imagine it gets fixed but only in Google Autofill and not Android auto fill

permalink
report
reply
19 points

I mean in their defense, apps really ought to have “normal” log-in screens. Providers working around that feels like a bandaid instead of a fix.

permalink
report
reply
17 points

That’s one thing I do like about iOS, there’s a secrets manager API and you can use their default keychain, or a 3rd party app like bitwarden and they all interface the same.

permalink
report
reply

Android

!android@lemmy.world

Create post

DROID DOES

Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules


1. All posts must be relevant to Android devices/operating system.


2. Posts cannot be illegal or NSFW material.


3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.


4. Non-whitelisted bots will be banned.


5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.


6. Memes are not allowed to be posts, but are allowed in the comments.


7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.


8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.


Community Resources:


We are Android girls*,

In our Lemmy.world.

The back is plastic,

It’s fantastic.

*Well, not just girls: people of all gender identities are welcomed here.


Our Partner Communities:

!android@lemmy.ml


Community stats

  • 2.7K

    Monthly active users

  • 824

    Posts

  • 5.9K

    Comments