search

bitwarden / mobile

Retired Bitwarden mobile app for iOS and Android (MAUI/Xamarin).
https://bitwarden.com
GNU General Public License v3.0
156 stars 25 forks source link

Autofill not working on Chrome Android #489

Closed 6w6OoPIRf3et9qT8tv7EyO1N5Y6RBqVD0zdY9ih closed 3 years ago

6w6OoPIRf3et9qT8tv7EyO1N5Y6RBqVD0zdY9ih commented 5 years ago

Autofill is not consistent and not working on chrome Android

Screenshot_20190422-021510 Screenshot_20190422-021354

pPmnBRRYhIemiuiy3VBYULJIzQyZaEvWMbCPH1P commented 5 years ago

I would suggest that is a Firefox issue, though that is the same behavior I have seen in all browsers. The autofill framework doesn't give the full URL of the website, only the base domain.

TTiQsP5XjnV7swCm7qfhygLCIkcG90kcP07zYz3 commented 5 years ago

@hmnd Yes, as I previously mentioned, Chrome is bugged which is why neither Bitwarden or LastPass work with it when using the autofill service. You will need to use the accessibility service until Google fixes the problem.

But as I was trying to say earlier - Lastpass does not have the problems you keep saying.. it's flawless for me with Chrome.. so therefore, is Chrome really the problem? How is Lastpass still working OK?

G2CYoVfwT7dNXTueXT01bdGZXxRmMj8Z3elu6JF commented 5 years ago

@ghhv If you try disabling accessibility perms for LastPass and only give it autofill, it will do the same thing as Bitwarden. It only works because of the accessibility service, not native autofill.

TTiQsP5XjnV7swCm7qfhygLCIkcG90kcP07zYz3 commented 5 years ago

@hmnd yes, I did all that.. I couldn't get Bitwarden to work with either service.

X8Y0VaT36pq6o9BRth8RRcnKwlE5Q7w9moAsnzI commented 5 years ago

I am certain I was having the same issues with the accessibility service in Chrome on Android.

The ‘com.google.chrome’ would happen using both, and in the case of the accessibility service often times I had to open it, close it and then open it again to get it to show any fields.

It was better than the auto fill service if I recall, but still glitchy as all hell. I had sync issues sometimes too. It was definitely not a consistent experience.

I’ve switched to iOS and dropped Google completely recently for a long list of reasons, and now shit just works.

Android users should just use Firefox.

hJyZLMFcE8hRUflvSamGE6K3FplJbZ2KqG66oEX commented 5 years ago

FYI I have the com.google.chrome issue with bitwarden whether i'm using the autofill or the accessibility (notification) from bitwarden in chrome or a webview that uses chrome (such as clicking a link in gmail).

Maybe a separate issue.

6TY1v4528MwobWoALlRyI36gl93PKkBe4GXXfez commented 5 years ago

It looks like Google is aware of this issue and have a fix. Here is the bug report.

h6f2myeXAHjZuls2pPTP7Ulj52Jj559IwPp6s3E commented 5 years ago

I am experiencing the same issues trying to use Bitwarden (v2.2.1) with Samsung Internet on Android (v9.4.00.45). Auto-fill and Accessibility Service do not show up/are not options when attempting to log into a website through the browser. I tested Bitwarden in the Microsoft Edge for Android (v40.0.4.3892) browser and it works perfectly fine which leads me to believe it is an issue with the Chromium browser in general.

Also, like others have mentioned, LastPass (v4.10.4395) works perfectly fine for Samsung Internet and Chrome on my device (Samsung Galaxy S10, Android P) so I'm not entirely sure what they are doing/implementing differently here.

G2CYoVfwT7dNXTueXT01bdGZXxRmMj8Z3elu6JF commented 5 years ago

@camlen92 if you read over the conversation here, you'll find that LastPass is using the accessibility service and autofill with LastPass still does not work. Samsung Internet is likely based on Chromium, so that is why you are seeing the issue there too. As you can see here: https://github.com/bitwarden/mobile/issues/489#issuecomment-525022516, the issue is already in the process of being fixed in Chromium.

h6f2myeXAHjZuls2pPTP7Ulj52Jj559IwPp6s3E commented 5 years ago

@camlen92 if you read over the conversation here, you'll find that LastPass is using the accessibility service and autofill with LastPass still does not work. Samsung Internet is likely based on Chromium, so that is why you are seeing the issue there too. As you can see here: #489 (comment), the issue is already in the process of being fixed in Chromium.

@hmnd, sorry I should have linked this reply from a Bitwarden dev about Samsung Internet. According to an older post on Reddit, devs says that Samsung Internet doesn't support Accessibility Services. See: Autofill in Samsung Internet Browser. If what you are saying is true, that LastPass is using the Accessibility Service, then why does LastPass seem to work just fine in Samsung Internet, but Bitwarden does not? I could not get Bitwarden's Accessibility Service to trigger in Samsung Internet nor Chrome for Android but LastPass triggers just fine? Am I missing something here?

I've attached screenshots to show what I am seeing using LastPass in both Samsung Internet and Chrome for Android. chrome_lastpass samsung_lastpass

hJyZLMFcE8hRUflvSamGE6K3FplJbZ2KqG66oEX commented 5 years ago

Interesting, it looks like the bug filed on chrome https://bugs.chromium.org/p/chromium/issues/detail?id=996402 is being worked on.

Chrome Canary https://play.google.com/store/apps/details?id=com.chrome.canary consistently opens the autofill popup for me, but it always says the vault is locked. When tapping on the autofill popup I am taken to my vault without having to unlock (I had previously unlocked it) and shown Items for com.chrome.canary rather than for the site i'm actually trying to login to. Still an improvement just to see the autofill popup working much more consistently.

Small update: Before finishing this comment I force closed both BitWarden and Chrome Canary and then opened BitWarden and unlocked my vault and then switched to Chrome Canary and visited a few websites. The autofill continues to appear consistently but now I'm shown the logins for com.chrome.canary no matter what login form the autofill opens for. Tapping to show my vault behaves as described above where I am shown Items for com.chrome.canary in BitWarden. So it's as if BitWarden is unable to tell which website chrome is accessing and instead is treating it as a non-browser app and using the package name.

U1i8puO3B24QWhP22xpCaCMxAyeDOnNOKZ0r4Xf commented 5 years ago

I have the same issue with autofill on Chrome Beta and Canary because that's what I use. and bitwarden treats it as a app and not a browser. Bitwarden should let us add custom browsers or just add these variants of chrome to their list of supported browsers.

FieVIX9ZVA13EYyedOhBYs8eoSpUxbLh9UAvaQc commented 5 years ago

I've tried enabling the Chrome flag "#enable-android-autofill-accessibility" and I fixed this problem on my phone.

U1i8puO3B24QWhP22xpCaCMxAyeDOnNOKZ0r4Xf commented 5 years ago

Looks like this is fixed now in Chrome 77.0.3865 and above. Tried it on Beta and Canary both works

G2CYoVfwT7dNXTueXT01bdGZXxRmMj8Z3elu6JF commented 5 years ago

Can confirm @hazre. Issue can probably be closed.

hJyZLMFcE8hRUflvSamGE6K3FplJbZ2KqG66oEX commented 5 years ago

Maybe keep the issue open until that version of chrome is released as stable?

10RAwWVcGnrVV8FX1Jh1DPYBQT1QWQfNdtasqvx commented 5 years ago

Chrome Canary solved the com.android.chrome issue for me, but the promt is still inconsistent. When forcing a chrome restart it then works again for a while.

Using Android Pie on OnePlus 5 and latest Bitwarden (Beta) aswell as latest Chrome Canary. Also tried messing with some chrome flags and autofill settings, but the inconsistent promt still persists.

When it works, it works very well and consistent for a while, but after some hours it suddenly doesn't work for no website anymore until I force restart chrome.

10RAwWVcGnrVV8FX1Jh1DPYBQT1QWQfNdtasqvx commented 5 years ago

If anyone has suggestions what else I can try, please don't hesitate to post them. I'd love to try some ideas, maybe there's some easy fix. Starts to get really annoying when every few hours the autofill promt stops appearing. The main problem is that the issue is hardly reproducable as it only happens after some unknown time.

lBBMHxA7k0IibbUvRXc1FUkY8sas9BI7EwKj4rA commented 5 years ago

Whats the difference between tapping the notification for the auto-fill and when there is the little popup near the password? Because the notification does work without any issues (at least for me) but the popup never does

X8Y0VaT36pq6o9BRth8RRcnKwlE5Q7w9moAsnzI commented 5 years ago

Chrome updated today to v77.0.3865.73 and now the auto fill framework prompt doesn't even popup anymore... I cannot even begin to stress how annoying this is.

G2CYoVfwT7dNXTueXT01bdGZXxRmMj8Z3elu6JF commented 5 years ago

@mite1200 I've been on Chrome Dev for a week or so and haven't had any issues with autofill there.

@andre-paulo98 The notification uses Android accessibility features, whereas the popup uses actual autofill.

@DougParker1992 Try installing Chrome Dev (v78) and see if that works for you.

X8Y0VaT36pq6o9BRth8RRcnKwlE5Q7w9moAsnzI commented 5 years ago

@hmnd Chrome Dev doesn't seem to show any autofill prompt either. :(

Back to accessibility service for me.

U8dREAxzSdDqtzDpAaWH2pPK0ROKqyNbvZqU09P commented 5 years ago

I am currently running into this issue as well, but I have found that enabling Chrome's "Save Passwords" setting fixes it. The only downside is that now both Bitwarden AND Chrome will offer to save passwords on a new login.

The same behavior is present with LastPass. If I disable "Save Passwords" in Chrome, LastPass will refuse to autofill as well.

10RAwWVcGnrVV8FX1Jh1DPYBQT1QWQfNdtasqvx commented 5 years ago

I am currently running into this issue as well, but I have found that enabling Chrome's "Save Passwords" setting fixes it. The only downside is that now both Bitwarden AND Chrome will offer to save passwords on a new login.

The same behavior is present with LastPass. If I disable "Save Passwords" in Chrome, LastPass will refuse to autofill as well.

Thanks for the tip, will also try and see if that helps for me too. Though I don't know if we have the same problem. It seems, that your autofill didn't work at all and enabling password saving did enable the prompt showing up. On my side, the problem is that it's inconsistent and often doesn't pop up after some hours anymore until i force restart chrome.

niNVYUN8m2XeZnKGe2gsEokTOLe1tONv4W3MNps commented 5 years ago

I've been testing a bunch of browsers and I've found that Bitwarden works with Android autofill flawlessly with Firefox browsers. Chrome, Brave, Edge and Opera all don't work most of the time. Can anyone else replicate this?

St7T0bGkIUQAesnYkOOoiNPiPUadpCbY1K8xZEG commented 5 years ago

Yes, same issue here. And as far as I can tell, the patch that would supposedly fix this has already landed (in at least 77.0.3865.66 and later).

aCf8v83wRTULaGpXa5Ndhxq0TOEvxjTjYOeoO2Z commented 5 years ago

Auto fill is not working properly with 3rd party apps on Android (Bitwarden, 1Password and LastPass), with Chrome or Firefox. Only Google auto fill is working perfectly, wonder why...

UEBqheEXswNNy6eAqlWCfgz0tGrd00waj4taxzV commented 5 years ago

With firefox and last updates, bitwarden is working again since a few months. Some glitches occured when displaying the pop up or the notification auto complete but It's working.

OLwX9zmdXhuaFJ1otpisGf9bTAT06J3vEoxKOpg commented 5 years ago

Has there been any updates on this? With the most recent stable version of Chrome from Google Play, I still can't get any autofill boxes to pop up. Are there any known workarounds (e.g. using a canary build or similar)?

X8Y0VaT36pq6o9BRth8RRcnKwlE5Q7w9moAsnzI commented 5 years ago

This was never resolved for me. I just gave up and use the accessibility service. I've owned numerous flagship android devices, and the autofill framework is never consistent and almost always never even works. :(

niNVYUN8m2XeZnKGe2gsEokTOLe1tONv4W3MNps commented 5 years ago

It works with Firefox but nothing else.

On Thu, 5 Dec. 2019, 05:46 Douglas Parker, notifications@github.com wrote:

This was never resolved for me. I just gave up and use the accessibility service. I've owned numerous flagship android devices, and the autofill framework is never consistent and almost always never even works. :(

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/bitwarden/mobile/issues/489?email_source=notifications&email_token=AM7WT7DQEYW2HNGVCFBN6CLQW73J7A5CNFSM4HHNVV52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF6CSYA#issuecomment-561785184, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM7WT7GA5P7YWFLWIMPVLZTQW73J7ANCNFSM4HHNVV5Q .

QYjZ5894lM9vv1o1ussC0tIEWwv6fCrCn4E5Qaw commented 4 years ago

I checked on news saying it to be an issue of Android 9 (and below) not providing enough API for autofill services to handle it in browsers, and it is fixed in Android 10. Not sure if that fix would involve any app side change but at least there's hope.

hJyZLMFcE8hRUflvSamGE6K3FplJbZ2KqG66oEX commented 4 years ago

@AkazaDorian that's good to hear. Do you happen to have any links to the news you saw this on? Maybe they have more helpful information.

QYjZ5894lM9vv1o1ussC0tIEWwv6fCrCn4E5Qaw commented 4 years ago

@nemchik Sorry I just double checked the news and that seems to be another thing, sorry for let you down 😂

Q4I2Z8SFBMVJ01WoLQKkLM4icG5vexo2HriB1S8 commented 4 years ago

This is an issue for me on Brave Browser. Chrome just worked on GitHub login. But nothing on Brave autofill.

X8Y0VaT36pq6o9BRth8RRcnKwlE5Q7w9moAsnzI commented 4 years ago

@kspearrin I'm not sure if you are aware, but this issue isn't resolved for most of us. The comment you left here leads me to believe that you think it is resolved. Unfortunately, this is not the case. =(

HSm8PgDlvROREQJRxw4Rd84zIbe2w2WY5R4GshC commented 4 years ago

For me the issue is actually resolved with Android 10, which I installed two days ago.

St7T0bGkIUQAesnYkOOoiNPiPUadpCbY1K8xZEG commented 4 years ago

It still doesn't work with any chromium based browser I've tried. Not Brave, Kiwi, Chrome Canary through stable. Only Firefox and Firefox preview.

X8Y0VaT36pq6o9BRth8RRcnKwlE5Q7w9moAsnzI commented 4 years ago

I switched to 1Password and don't have any issues at all anymore. It might cost a bit more, but it's a small price to pay to not have to deal with this.

I really wanted to like Bitwarden, but I'm tired of dealing with autofill issues.

wYnXPZO3KnxsHT5aR7l289DUvAnkkO5UaRO2J4P commented 4 years ago

https://bugs.chromium.org/p/chromium/issues/detail?id=1014945 https://bugs.chromium.org/p/chromium/issues/detail?id=1015381

The issues were reported but Chrome devs didn't pick them up yet. You can try commenting on the issues to make them aware.

@DougParker1992 Can you try the instructions here with 1Password? It should stop working then similar to Bitwarden.

EDIT: I just tried it again and the issue is gone. It might've been fixed in Android 10.

X8Y0VaT36pq6o9BRth8RRcnKwlE5Q7w9moAsnzI commented 4 years ago

@quthla Hey, I tried reproducing that issue with 1Password and I was not able to reproduce it. Everything just worked flawlessly.

I also don't use the in-app web view. I always disable that and have hyperlinks open in Chrome directly.

I did enable the in-app web view with Gmail just to see if that bug appeared for 1Password too, but it wasn't the case. At least for me.

Chromium Issue 1015381 involves using an in-app web view, which I never use so I imagine it is unrelated to this bug.

Chromium Issue 1014945 seems to do with Chrome and performance degradation. Also unrelated to this issue.

Thanks for trying to help! :)

EDIT:

EDIT: I just tried it again and the issue is gone. It might've been fixed in Android 10.

I am on version 9 of Android still, so probably not related to the Android version difference.

wYnXPZO3KnxsHT5aR7l289DUvAnkkO5UaRO2J4P commented 4 years ago

@DougParker1992 Can you try to reproduce it with Bitwarden again using the same steps? Just to make sure it wasn't fixed (by accident) in newer versions of Chrome.

And yes, it also stopped working randomly without using an in-app webview but that was one way to safely reproduce it.

X8Y0VaT36pq6o9BRth8RRcnKwlE5Q7w9moAsnzI commented 4 years ago

@quthla I reinstalled Bitwarden and disabled 1Password.

Auto fill popped up once when I opened a web page in the in-app web view in Gmail. Switched over to Chrome, no auto fill prompt. Switched back to Gmail and the auto fill prompt wouldn't appear again. I even force stopped Chrome and it wouldn't show back up.

Similar as before really. I see the auto fill prompt for Bitwarden once and then I don't see it again for days or even weeks.

wYnXPZO3KnxsHT5aR7l289DUvAnkkO5UaRO2J4P commented 4 years ago

That is indeed weird. Restarting Chrome always made it work again.

And you don't have 1Password enabled for accessibility? Just autofill?

X8Y0VaT36pq6o9BRth8RRcnKwlE5Q7w9moAsnzI commented 4 years ago

That is indeed weird. Restarting Chrome always made it work again.

And you don't have 1Password enabled for accessibility? Just autofill?

Actually, I did have the accessibility service enabled for 1Password. I didn't realize it, because it worked so well with a prompt appearing for a password fill.

Bitwardens accessibility service requires me to swipe from the top and look for it's notification to fill, which became really annoying when half the time it tries filling for com.android.chrome

EDIT: After the accessibility service tries filling for the web browser instead of the website, I have to back out and then reswipe down, hit the notification, unlock, and then fill again. It just got really annoying and that's why I switched. If it ever gets better I'm sure I will come back and host an on premise install again.

aVAXD37bgoxgygSrAhQRxc6MBdA1uIF3rCyfptM commented 4 years ago

Hi everyone, just wanted to chime in to say that I'm having the exact same issue. Accessibility service disabled, since that's how it's supposed to be, and only relying on the autofill framework. Result: getting autofill on forms in a consistent way only when using Firefox (including preview and focus), but with chromium browsers it's a hit and miss. This includes chrome, Brave, kiwi, opera. Also working unreliably or not working at all: Samsung internet browser, Ms Edge, Xiaomi Mi browser and Via browser. I must've tested another bunch but none work (they're pretty much all based on chromium, I guess).

Considering that I've moved from k2a to Bitwarden because of browser autofill issues on Android, this situation is a bit ironic. Is there ANY other password manager on Android that works on chromium browsers JUST by relying on the autofill fwk? Without accessibility service.

Knowing that could suggest if the issue is with Bitwarden or with chrome (or worse, with the OS itself). I'm using a Pixel 2 XL running Android 10, so no weird rom "battery" optimisations, only the stock Adaptive Battery feature enabled and doze mode enabled as well of course.

Thanks!

aVAXD37bgoxgygSrAhQRxc6MBdA1uIF3rCyfptM commented 4 years ago

That is indeed weird. Restarting Chrome always made it work again. And you don't have 1Password enabled for accessibility? Just autofill?

Actually, I did have the accessibility service enabled for 1Password. I didn't realize it, because it worked so well with a prompt appearing for a password fill.

Bitwardens accessibility service requires me to swipe from the top and look for it's notification to fill, which became really annoying when half the time it tries filling for com.android.chrome

EDIT: After the accessibility service tries filling for the web browser instead of the website, I have to back out and then reswipe down, hit the notification, unlock, and then fill again. It just got really annoying and that's why I switched. If it ever gets better I'm sure I will come back and host an on premise install again.

So even with 1password the autofill is broken unless you have the accessibility service running? Is my understanding correct?

P82N2E6tigTQR0PZQ69jVtDRNeFS5hv6Biwtl5V commented 4 years ago

Just tested on my Sony with Android 8 every combination of Firefox - Chrome 1Password - Bitwarden Autofill - Accessibility Service

Autofill on Chrome (currently version 79.0.3945.93) doesn't work, for both 1Password and Bitwarden. Autofill on Firefox (currently version 68.3.0) works, for both 1Password and Bitwarden. Accessibility Service always works, but I had to disable both "Scan" options and keep the persistent notification, cause the performance would drop drastically otherwise, and even so it gets a bit clunky at times (sometimes I tap the notification and it gets stuck at the bitwarden splash logo, sometimes it loads filtering by "com.android.chrome"). I'm stuck with this suboptimal solution for now, hoping that a fix may ever be found for the Auto fill on Chrome.

X8Y0VaT36pq6o9BRth8RRcnKwlE5Q7w9moAsnzI commented 4 years ago

That is indeed weird. Restarting Chrome always made it work again. And you don't have 1Password enabled for accessibility? Just autofill?

Actually, I did have the accessibility service enabled for 1Password. I didn't realize it, because it worked so well with a prompt appearing for a password fill. Bitwardens accessibility service requires me to swipe from the top and look for it's notification to fill, which became really annoying when half the time it tries filling for com.android.chrome EDIT: After the accessibility service tries filling for the web browser instead of the website, I have to back out and then reswipe down, hit the notification, unlock, and then fill again. It just got really annoying and that's why I switched. If it ever gets better I'm sure I will come back and host an on premise install again.

So even with 1password the autofill is broken unless you have the accessibility service running? Is my understanding correct?

@andreaippo It is my understanding that the auto fill framework is broken for all password managers that are not using Firefox. It also seemed to work fine on Safari for iPhone.

aVAXD37bgoxgygSrAhQRxc6MBdA1uIF3rCyfptM commented 4 years ago

@DougParker1992 Thanks. Found this issue on the chromium bug tracker: https://bugs.chromium.org/p/chromium/issues/detail?id=849774&q=Autofill%20framework&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified

Hasn't received much love from Devs so far, might be worth starring and commenting, maybe?