The latest Android APP (2.3.1) cannot automatically fill in the account and password. #956

@Picasso59 commented on GitHub (Mar 20, 2020):

A follow up to my earlier posts. The problem eventually reappeared with Chrome 80...149. However, I disabled the accessibility setting and left the overlay setting active. This has it working again for me.

Perhaps of interest to the Devs, before I disabled accessibility, I found that clearing the phone's "recent items" allowed it to work temporarily.

@Picasso59 commented on GitHub (Mar 20, 2020): A follow up to my earlier posts. The problem eventually reappeared with Chrome 80...149. However, I disabled the accessibility setting and left the overlay setting active. This has it working again for me. Perhaps of interest to the Devs, before I disabled accessibility, I found that clearing the phone's "recent items" allowed it to work temporarily.

GiteaMirror commented

@jeffshead commented on GitHub (Mar 20, 2020):

Android Pie on Pixel XL

Same issues that I reported here (https://github.com/bitwarden/mobile/issues/683), with videos, still exist. The only difference with v2.3.1, is that the pop-up to select the vault is now persistent but auto-fill failures are much more frequent. Actually, the pop-up usually remains on the screen when it should not and it is usually in the way and covering the form submission button. I've even seen the pop-up remain on the Android home screen when there is no app or form present. The persistent notification option was less intrusive -- I wish that was still an option.

Sometimes auto-fill works. Sometimes I have to perform the [touch the persistent Auto-fill with Bitwarden pop-up on the form and then select the correct login from the vault] cycle 4-5 times before it finally fills the form.

If I'm already logged into the Android BW app, the list of matching logins still flashes above the persistent pop-up for a split-second and disappears as depicted in the videos I mentioned above.

Sometimes when I touch the persistent Auto-fill with Bitwarden pop-up on the form and then select the correct login from the vault, I'm brought back to the form with a list of matching logins above the persistent Auto-fill with Bitwarden pop-up rather than the form being auto-filled, as it should be.

Unfortunatly, this latest update makes using BW on Android MORE inconvenient for many of us.

@jeffshead commented on GitHub (Mar 20, 2020): **Android Pie on Pixel XL** Same issues that I reported here (https://github.com/bitwarden/mobile/issues/683), with videos, still exist. The only difference with v2.3.1, is that the pop-up to select the vault is now persistent but auto-fill failures are much more frequent. Actually, the pop-up usually remains on the screen when it should not and it is usually in the way and covering the form submission button. I've even seen the pop-up remain on the Android home screen when there is no app or form present. The persistent notification option was less intrusive -- I wish that was still an option. Sometimes auto-fill works. Sometimes I have to perform the [touch the persistent _**Auto-fill with Bitwarden**_ pop-up on the form and then select the correct login from the vault] cycle 4-5 times before it finally fills the form. If I'm already logged into the Android BW app, the list of matching logins still flashes above the persistent pop-up for a split-second and disappears as depicted in the videos I mentioned above. Sometimes when I touch the persistent _**Auto-fill with Bitwarden**_ pop-up on the form and then select the correct login from the vault, I'm brought back to the form with a list of matching logins above the persistent _**Auto-fill with Bitwarden**_ pop-up rather than the form being auto-filled, as it should be. Unfortunatly, this latest update makes using BW on Android MORE inconvenient for many of us.

GiteaMirror commented

@THEOCKID commented on GitHub (Mar 21, 2020):

Got that same "flash and gone" on my samsung galaxy S20+ but I'm running Opera 56.1.2780.59589 . I never run Chrome.

@THEOCKID commented on GitHub (Mar 21, 2020): Got that same "flash and gone" on my samsung galaxy S20+ but I'm running Opera 56.1.2780.59589 . I never run Chrome.

GiteaMirror commented

2025-11-26 22:35:00 -06:00

@THEOCKID commented on GitHub (Mar 21, 2020):

Also, I downgraded by BW to 2.2.8 (2136) and it works fine; gives me 3 options For Auto-fill Accessibility Service: Always Scan (off), Persist Notification (on, which seems to work best for me) and Scan When Password Field Focused). If I recall correctly, none of these 3 options were available on the newest BW release. :(

@THEOCKID commented on GitHub (Mar 21, 2020): Also, I downgraded by BW to 2.2.8 (2136) and it works fine; gives me 3 options For Auto-fill Accessibility Service: Always Scan (off), Persist Notification (on, which seems to work best for me) and Scan When Password Field Focused). If I recall correctly, none of these 3 options were available on the newest BW release. :(

GiteaMirror commented

@THEOCKID commented on GitHub (Mar 21, 2020):

Sorry, guess I'm too old to be a beta-tester anymore. BW is mission-critical to me, it's gotta be stable.

@THEOCKID commented on GitHub (Mar 21, 2020): Sorry, guess I'm too old to be a beta-tester anymore. BW is mission-critical to me, it's gotta be stable.

GiteaMirror commented

2025-11-26 22:35:00 -06:00

@immanuelfodor commented on GitHub (Mar 22, 2020):

Same issue as OP, the small popup under the form input appears, then immediately disappears, can't fill the form as I have zero time to tap on it. Oneplus 7

@immanuelfodor commented on GitHub (Mar 22, 2020): Same issue as OP, the small popup under the form input appears, then immediately disappears, can't fill the form as I have zero time to tap on it. Oneplus 7

GiteaMirror commented

2025-11-26 22:35:00 -06:00

@immanuelfodor commented on GitHub (Mar 22, 2020):

Here it is on sceen record.

Brave (Chromium): https://sendvid.com/75dgxgh8
Firefox: https://sendvid.com/dr6ljjgx

@immanuelfodor commented on GitHub (Mar 22, 2020): Here it is on sceen record. Brave (Chromium): https://sendvid.com/75dgxgh8 Firefox: https://sendvid.com/dr6ljjgx

GiteaMirror commented

2025-11-26 22:35:01 -06:00

@tomo92s commented on GitHub (Mar 22, 2020):

Please restore old notification option

@tomo92s commented on GitHub (Mar 22, 2020): Please restore old notification option

GiteaMirror commented

2025-11-26 22:35:01 -06:00

@guiggs commented on GitHub (Mar 22, 2020):

I'm having the exactly same problem. Samsung S8 with Android 9. Doesn't work on Firefox, Kiwi or Bromite.

@guiggs commented on GitHub (Mar 22, 2020): I'm having the exactly same problem. Samsung S8 with Android 9. Doesn't work on Firefox, Kiwi or Bromite.

GiteaMirror commented

2025-11-26 22:35:01 -06:00

@tomo92s commented on GitHub (Mar 23, 2020):

I think is over...;/

@tomo92s commented on GitHub (Mar 23, 2020): ![IMG_20200322_121700](https://user-images.githubusercontent.com/32452522/77287880-e3456b00-6cd6-11ea-81ba-1f11083272bb.jpg) I think is over...;/

GiteaMirror commented

@lfrancke commented on GitHub (Mar 24, 2020):

It works for me on a Samsung Galaxy Tab 3 (Android 9) but it doesn't work with a Pixel 4 (Android 10). Both of them unmodified (no root etc.).

On the tablet it doesn't work reliably though and the experience is noticeably worse than before. In many apps the username and password fields are on separate dialogs. I only get the popup for the password field. For the username I don't get anything and have to manually open the app and manually search & copy in there.

The option for the persistent notification is gone which would have made this a bit easier.

Happy to provide more input, the way it is currently working makes the app basically unusable for my devices.

@lfrancke commented on GitHub (Mar 24, 2020): It works for me on a Samsung Galaxy Tab 3 (Android 9) but it doesn't work with a Pixel 4 (Android 10). Both of them unmodified (no root etc.). On the tablet it doesn't work reliably though and the experience is noticeably worse than before. In many apps the username and password fields are on separate dialogs. I only get the popup for the password field. For the username I don't get anything and have to manually open the app and manually search & copy in there. The option for the persistent notification is gone which would have made this a bit easier. Happy to provide more input, the way it is currently working makes the app basically unusable for my devices.

GiteaMirror commented

@MeiRos commented on GitHub (Mar 26, 2020):

Same problem with Honor 8A and Bromite.
Does anyone have an idea, why this happens?

@MeiRos commented on GitHub (Mar 26, 2020): Same problem with Honor 8A and Bromite. Does anyone have an idea, why this happens?

GiteaMirror commented

@immanuelfodor commented on GitHub (Mar 28, 2020):

Do you guys know any workaround or temporary fix? This bug is one of the most annoying I've ever had.

@immanuelfodor commented on GitHub (Mar 28, 2020): Do you guys know any workaround or temporary fix? This bug is one of the most annoying I've ever had.

GiteaMirror commented

2025-11-26 22:35:03 -06:00

@tomo92s commented on GitHub (Mar 28, 2020):

Do you guys know any workaround or temporary fix? This bug is one of the most annoying I've ever had.

Back to v2.2.8, create clone and that's it

@tomo92s commented on GitHub (Mar 28, 2020): > Do you guys know any workaround or temporary fix? This bug is one of the most annoying I've ever had. Back to v2.2.8, create clone and that's it

GiteaMirror commented

@thethomasboyer commented on GitHub (Mar 29, 2020):

Same problem here.

The pop-up appears, then vanishes in about ~five nanoseconds.

Since it's the only secure and usable way of using BW (to my knowledge), it's quite annoying...

(Firefox 68.6.0, SM-N975F, Android 10)

edit: I am now unable to reproduce this disappearing behavior, although the pop-up does flicker a lot, and sometimes lands at a weird location of my screen.

@thethomasboyer commented on GitHub (Mar 29, 2020): Same problem here. The pop-up appears, then vanishes in about ~five nanoseconds. Since it's the only secure and usable way of using BW (to my knowledge), it's quite annoying... (Firefox 68.6.0, SM-N975F, Android 10) edit: I am now unable to reproduce this disappearing behavior, although the pop-up does flicker a lot, and sometimes lands at a weird location of my screen.

GiteaMirror commented

2025-11-26 22:35:03 -06:00

@ghost commented on GitHub (Mar 29, 2020):

Please bring back the old system as an option, especially the consistent notification version because that was the most reliable. I'm going to use the outdated client for now.

@ghost commented on GitHub (Mar 29, 2020): Please bring back the old system as an option, especially the consistent notification version because that was the most reliable. I'm going to use the outdated client for now.

GiteaMirror commented

2025-11-26 22:35:03 -06:00

@mateusz-owczarek commented on GitHub (Mar 31, 2020):

I have the same problem. Device info:

Galaxy S7 (SM-G930F)
Chrome 80.0.3987.149
Android 8.0.0
Bitwarden 2.3.1

@mateusz-owczarek commented on GitHub (Mar 31, 2020): I have the same problem. Device info: - Galaxy S7 (SM-G930F) - Chrome 80.0.3987.149 - Android 8.0.0 - Bitwarden 2.3.1

GiteaMirror commented

@MisteurZZ commented on GitHub (Apr 1, 2020):

Same problem, with a Huawei P30 Pro, android 10.
Issue with 2.3.1 or 2.3
So i've downgraded to 2.2.8

@MisteurZZ commented on GitHub (Apr 1, 2020): Same problem, with a Huawei P30 Pro, android 10. Issue with 2.3.1 or 2.3 So i've downgraded to 2.2.8

GiteaMirror commented

@Nyar233 commented on GitHub (Apr 4, 2020):

You can try giving the bitwarden app permission to pop up in the background.

@Nyar233 commented on GitHub (Apr 4, 2020): You can try giving the bitwarden app permission to pop up in the background.

GiteaMirror commented

@tomo92s commented on GitHub (Apr 4, 2020):

You can try giving the bitwarden app permission to pop up in the background.

That not working. This is app issue

@tomo92s commented on GitHub (Apr 4, 2020): > You can try giving the bitwarden app permission to pop up in the background. That not working. This is app issue

GiteaMirror commented

@bayasdev commented on GitHub (Apr 5, 2020):

Autofill is working for me but it doesn't detects Vivaldi Snapshot 2.12 (com.vivaldi.browser.snapshot) as a browser app thus showing results only for vivaldi.net.

Android App: 2.3.1
Android: One UI 2 with Android 10
Device: SM-G970F

@bayasdev commented on GitHub (Apr 5, 2020): Autofill is working for me but it doesn't detects Vivaldi Snapshot 2.12 (com.vivaldi.browser.snapshot) as a browser app thus showing results only for vivaldi.net. Android App: 2.3.1 Android: One UI 2 with Android 10 Device: SM-G970F

GiteaMirror commented

@superm1 commented on GitHub (Apr 6, 2020):

Since #715 got duplicated here, just to leave this link for people. This looks to be an Android autofill service or chrome issue:
https://bugs.chromium.org/p/chromium/issues/detail?id=1015381

It happens in a variety of browsers and often restarting the browser kicks it back to life.

@superm1 commented on GitHub (Apr 6, 2020): Since #715 got duplicated here, just to leave this link for people. _This looks to be an Android autofill service or chrome issue_: https://bugs.chromium.org/p/chromium/issues/detail?id=1015381 It happens in a variety of browsers and often restarting the browser kicks it back to life.

GiteaMirror commented

@immanuelfodor commented on GitHub (Apr 6, 2020):

Since it worked one version earlier on a variety of browsers, and only Bitwarden got updated in the meantime, and it works again when downgraded on the same set of browsers, I don't think its a Chrome/FF issue, the change mentioned in the release notes (rewrite) is what doesn't work.

@immanuelfodor commented on GitHub (Apr 6, 2020): Since it worked one version earlier on a variety of browsers, and only Bitwarden got updated in the meantime, and it works again when downgraded on the same set of browsers, I don't think its a Chrome/FF issue, the change mentioned in the release notes (rewrite) is what doesn't work.

GiteaMirror commented

@Picasso59 commented on GitHub (Apr 6, 2020):

I posted nearly 3 weeks ago when I was having this problem. I've had it working (almost) since then.

I switched off all the autofill permissions and switched off my phone. I restarted into Recovery and wipe the cache partition. When the phone restarted I enabled all the Bitwrden autofill permissions.

I'm now on Chrome 80.0.3987.162 (Oneplus 6T Android 10)

The only anomaly I'm seeing is that a grey box occasionally shows for a few seconds asking me to enable autofill, which it already is. However, BW is mainly usably.

@Picasso59 commented on GitHub (Apr 6, 2020): I posted nearly 3 weeks ago when I was having this problem. I've had it working (almost) since then. I switched off all the autofill permissions and switched off my phone. I restarted into Recovery and wipe the cache partition. When the phone restarted I enabled all the Bitwrden autofill permissions. I'm now on Chrome 80.0.3987.162 (Oneplus 6T Android 10) The only anomaly I'm seeing is that a grey box occasionally shows for a few seconds asking me to enable autofill, which it already is. However, BW is mainly usably.

GiteaMirror commented

2025-11-26 22:35:06 -06:00

@superm1 commented on GitHub (Apr 6, 2020):

Since it worked one version earlier on a variety of browsers, and only Bitwarden got updated in the meantime, and it works again when downgraded on the same set of browsers, I don't think its a Chrome/FF issue, the change mentioned in the release notes (rewrite) is what doesn't work.

The thing is it's intermittent - particularly if the browser has been running a while. There have been several instances that someone claims "Upgrading chrome fixed it for me"! Upgrading the app typically kills the process and restarts it, so that's why it works for a bit.
And sure enough I upgrade too and it's working for a short period of time. Then eventually I switch apps, or come into the browser another way and the issue happens again.

And this has been a problem with LP and Bitwarden both for me. I experienced it with LP and continue to experience with Bitwarden.

@superm1 commented on GitHub (Apr 6, 2020): > Since it worked one version earlier on a variety of browsers, and only Bitwarden got updated in the meantime, and it works again when downgraded on the same set of browsers, I don't think its a Chrome/FF issue, the change mentioned in the release notes (rewrite) is what doesn't work. The thing is it's intermittent - particularly if the browser has been running a while. There have been several instances that someone claims "Upgrading chrome fixed it for me"! Upgrading the app typically kills the process and restarts it, so that's why it works for a bit. And sure enough I upgrade too and it's working _for a short period of time_. Then eventually I switch apps, or come into the browser another way and the issue happens again. And this has been a problem with LP and Bitwarden both for me. I experienced it with LP and continue to experience with Bitwarden.

GiteaMirror commented

@mpbw2 commented on GitHub (Apr 6, 2020):

Here's a link to a recent build containing some accessibility fixes (since it's taking too long for Google to approve beta releases). I'd be interested if this improves the accessibility overlay's behavior for you guys.

[Edit: link removed, latest Google Play beta contains fixes]

@mpbw2 commented on GitHub (Apr 6, 2020): Here's a link to a recent build containing some accessibility fixes (since it's taking too long for Google to approve beta releases). I'd be interested if this improves the accessibility overlay's behavior for you guys. [Edit: link removed, latest Google Play beta contains fixes]

GiteaMirror commented

2025-11-26 22:35:06 -06:00

@superm1 commented on GitHub (Apr 6, 2020):

(FYI My comments above were not based on the accessibility overlay; they were for native android password filling API)

@superm1 commented on GitHub (Apr 6, 2020): (FYI My comments above were not based on the accessibility overlay; they were for native android password filling API)

GiteaMirror commented

2025-11-26 22:35:06 -06:00

@tomo92s commented on GitHub (Apr 6, 2020):

Here's a link to a recent build containing some accessibility fixes (since it's taking too long for Google to approve beta releases). I'd be interested if this improves the accessibility overlay's behavior for you guys.

[Edit: link removed, latest Google Play beta contains fixes]

Still not working (Redmi Note 4X - Android 7.0)

@tomo92s commented on GitHub (Apr 6, 2020): > Here's a link to a recent build containing some accessibility fixes (since it's taking too long for Google to approve beta releases). I'd be interested if this improves the accessibility overlay's behavior for you guys. > > [Edit: link removed, latest Google Play beta contains fixes] Still not working (Redmi Note 4X - Android 7.0)

GiteaMirror commented

@ratenfanger commented on GitHub (Apr 6, 2020):

Here's a link to a recent build containing some accessibility fixes (since it's taking too long for Google to approve beta releases). I'd be interested if this improves the accessibility overlay's behavior for you guys.

[Edit: link removed, latest Google Play beta contains fixes]

I had the same problems as described in this issue. I tried this version for some minutes and all sites which did not work before are working flawlessly now!

Great work! Thank you very much!

Using Firefox on Android 8.1.

@ratenfanger commented on GitHub (Apr 6, 2020): > Here's a link to a recent build containing some accessibility fixes (since it's taking too long for Google to approve beta releases). I'd be interested if this improves the accessibility overlay's behavior for you guys. > > [Edit: link removed, latest Google Play beta contains fixes] I had the same problems as described in this issue. I tried this version for some minutes and all sites which did not work before are working flawlessly now! Great work! Thank you very much! Using Firefox on Android 8.1.

GiteaMirror commented

@Picasso59 commented on GitHub (Apr 6, 2020):

Here's a link to a recent build containing some accessibility fixes (since it's taking too long for Google to approve beta releases). I'd be interested if this improves the accessibility overlay's behavior for you guys.

It seems to be working as before. See my comment above. I still get an intermittent warning at the bottom of my screen relating to the Autofill Accessibility Service. It is enabled with permission granted. It doesn't seem to affect the working of BW but it would seem to be an incorrect warning.

@Picasso59 commented on GitHub (Apr 6, 2020): > Here's a link to a recent build containing some accessibility fixes (since it's taking too long for Google to approve beta releases). I'd be interested if this improves the accessibility overlay's behavior for you guys. It seems to be working as before. See my comment above. I still get an intermittent warning at the bottom of my screen relating to the Autofill Accessibility Service. It is enabled with permission granted. It doesn't seem to affect the working of BW but it would seem to be an incorrect warning.

GiteaMirror commented

@jeffshead commented on GitHub (Apr 6, 2020):

BW on my Pixel XL has always been really flaky. Even with this latest v2.3.1 (2295) beta. It seems to behave exactly as the previous version. The auto-fill box never appears sometimes. Sometimes if flashes a couple of times and stays on the screen and sometimes it flashes and does not come back.

I still get the gray pop-up, intermittently, that says “BW needs your attention -- see auto-fill accessibility service…” even though both BW settings are enabled and BW is the only auto-fill enabled app on the phone.

Sometimes I also get, “No items in your vault for --“even though matching logins do exist and they do work most of the time. Sometimes auto-fill sees a match but it does not fill in any fields. Sometimes it fills in only the username, sometimes in fills in both the username and password.

Roboform worked nearly perfect on the same phone so I can’t see this being a phone issue or a conflict with something else.

@jeffshead commented on GitHub (Apr 6, 2020): BW on my Pixel XL has always been really flaky. Even with this latest v2.3.1 (2295) beta. It seems to behave exactly as the previous version. The auto-fill box never appears sometimes. Sometimes if flashes a couple of times and stays on the screen and sometimes it flashes and does not come back. I still get the gray pop-up, intermittently, that says “BW needs your attention -- see auto-fill accessibility service…” even though both BW settings are enabled and BW is the only auto-fill enabled app on the phone. Sometimes I also get, “No items in your vault for --“even though matching logins do exist and they do work most of the time. Sometimes auto-fill sees a match but it does not fill in any fields. Sometimes it fills in only the username, sometimes in fills in both the username and password. Roboform worked nearly perfect on the same phone so I can’t see this being a phone issue or a conflict with something else.

GiteaMirror commented

@mpbw2 commented on GitHub (Apr 6, 2020):

Thanks everyone for the feedback. If you haven't already can you specify if you're using the autofill service, the autofill accessibility service, or both?

@mpbw2 commented on GitHub (Apr 6, 2020): Thanks everyone for the feedback. If you haven't already can you specify if you're using the autofill service, the autofill accessibility service, or both?

GiteaMirror commented

@MisteurZZ commented on GitHub (Apr 6, 2020):

Here's a link to a recent build containing some accessibility fixes (since it's taking too long for Google to approve beta releases). I'd be interested if this improves the accessibility overlay's behavior for you guys.

[Edit: link removed, latest Google Play beta contains fixes]

It seems to work for me.
Thanx

@MisteurZZ commented on GitHub (Apr 6, 2020): > Here's a link to a recent build containing some accessibility fixes (since it's taking too long for Google to approve beta releases). I'd be interested if this improves the accessibility overlay's behavior for you guys. > > [Edit: link removed, latest Google Play beta contains fixes] It seems to work for me. Thanx

GiteaMirror commented

@jeffshead commented on GitHub (Apr 6, 2020):

Both. Fills fewer forms with only one enabled.

On Mon, Apr 6, 2020, 2:30 PM Matt Portune notifications@github.com wrote:

Thanks everyone for the feedback. If you haven't already can you specify
if you're using the autofill service, the autofill accessibility service,
or both?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bitwarden/mobile/issues/784#issuecomment-609963266,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACVLU6LNDQRD3GUK4WHOEDRLINVHANCNFSM4LO75HAA
.

@jeffshead commented on GitHub (Apr 6, 2020): Both. Fills fewer forms with only one enabled. On Mon, Apr 6, 2020, 2:30 PM Matt Portune <notifications@github.com> wrote: > Thanks everyone for the feedback. If you haven't already can you specify > if you're using the autofill service, the autofill accessibility service, > or both? > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/bitwarden/mobile/issues/784#issuecomment-609963266>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AACVLU6LNDQRD3GUK4WHOEDRLINVHANCNFSM4LO75HAA> > . >

GiteaMirror commented

@Picasso59 commented on GitHub (Apr 6, 2020):

Thanks everyone for the feedback. If you haven't already can you specify if you're using the autofill service, the autofill accessibility service, or both?

Using both.

@Picasso59 commented on GitHub (Apr 6, 2020): > Thanks everyone for the feedback. If you haven't already can you specify if you're using the autofill service, the autofill accessibility service, or both? Using both.

GiteaMirror commented

@mpbw2 commented on GitHub (Apr 6, 2020):

BTW if you're on Android 7.0+ we added an Auto-fill tile to the quick settings panel. Since it's always present (once enabled) it will function like the old auto-fill notification, except without the battery drain.

@mpbw2 commented on GitHub (Apr 6, 2020): BTW if you're on Android 7.0+ we added an Auto-fill tile to the quick settings panel. Since it's always present (once enabled) it will function like the old auto-fill notification, except without the battery drain.

GiteaMirror commented

@tomo92s commented on GitHub (Apr 7, 2020):

BTW if you're on Android 7.0+ we added an Auto-fill tile to the quick settings panel. Since it's always present (once enabled) it will function like the old auto-fill notification, except without the battery drain.

So when can we expect a fix? On my Redmi Note 4X with Android 7.0 notification still not appearing. I had to go back to version 2.2.8.

@tomo92s commented on GitHub (Apr 7, 2020): > BTW if you're on Android 7.0+ we added an Auto-fill tile to the quick settings panel. Since it's always present (once enabled) it will function like the old auto-fill notification, except without the battery drain. So when can we expect a fix? On my Redmi Note 4X with Android 7.0 notification still not appearing. I had to go back to version 2.2.8.

GiteaMirror commented

https://www.gadgetdetail.com/xiaomi-redmi-note-4-change-quick-toggles-notification-bar/

@mpbw2 commented on GitHub (Apr 7, 2020):

On my Redmi Note 4X with Android 7.0 notification still not appearing.

The quick settings tile isn't a notification, it's a tile that you have to enable it via the quick settings panel.
Google led me here for the Redmi Note 4X:

@mpbw2 commented on GitHub (Apr 7, 2020): > On my Redmi Note 4X with Android 7.0 notification still not appearing. The quick settings tile isn't a notification, it's a tile that you have to enable it via the quick settings panel. Google led me here for the Redmi Note 4X: https://www.gadgetdetail.com/xiaomi-redmi-note-4-change-quick-toggles-notification-bar/

GiteaMirror commented

@tomo92s commented on GitHub (Apr 7, 2020):

On my Redmi Note 4X with Android 7.0 notification still not appearing.

The quick settings tile isn't a notification, it's a tile that you have to enable it via the quick settings panel.
Google led me here for the Redmi Note 4X:

https://www.gadgetdetail.com/xiaomi-redmi-note-4-change-quick-toggles-notification-bar/

I don't have this option

@tomo92s commented on GitHub (Apr 7, 2020): > > On my Redmi Note 4X with Android 7.0 notification still not appearing. > > The quick settings tile isn't a notification, it's a tile that you have to enable it via the quick settings panel. > Google led me here for the Redmi Note 4X: > > https://www.gadgetdetail.com/xiaomi-redmi-note-4-change-quick-toggles-notification-bar/ I don't have this option

GiteaMirror commented

@qw4096 commented on GitHub (Apr 7, 2020):

Here's a link to a recent build containing some accessibility fixes (since it's taking too long for Google to approve beta releases). I'd be interested if this improves the accessibility overlay's behavior for you guys.

[Edit: link removed, latest Google Play beta contains fixes]

Thanks, it's working now

@qw4096 commented on GitHub (Apr 7, 2020): > > > Here's a link to a recent build containing some accessibility fixes (since it's taking too long for Google to approve beta releases). I'd be interested if this improves the accessibility overlay's behavior for you guys. > > [Edit: link removed, latest Google Play beta contains fixes] Thanks, it's working now

GiteaMirror commented

@mpbw2 commented on GitHub (Apr 8, 2020):

@Picasso59 @jeffshead Can you provide some examples of websites and/or apps that trigger the behavior you're seeing?

@mpbw2 commented on GitHub (Apr 8, 2020): @Picasso59 @jeffshead Can you provide some examples of websites and/or apps that trigger the behavior you're seeing?

GiteaMirror commented

@Picasso59 commented on GitHub (Apr 8, 2020):

@Picasso59 @jeffshead Can you provide some examples of websites and/or apps that trigger the behavior you're seeing?

It is intermittent. I don't recall any apps but I use fingerprint login for my most used ones.

https://bbc.co.uk If I try to sign in to my account, usually when I touch the password box, I will see the BW warning. It is intermittent as I say. Refreshing the page can sometimes show the alert. It happens when BW is both locked and unlocked.

@Picasso59 commented on GitHub (Apr 8, 2020): > @Picasso59 @jeffshead Can you provide some examples of websites and/or apps that trigger the behavior you're seeing? It is intermittent. I don't recall any apps but I use fingerprint login for my most used ones. https://bbc.co.uk If I try to sign in to my account, usually when I touch the password box, I will see the BW warning. It is intermittent as I say. Refreshing the page can sometimes show the alert. It happens when BW is both locked and unlocked.

GiteaMirror commented

@Picasso59 commented on GitHub (Apr 8, 2020):

@Picasso59 @jeffshead Can you provide some examples of websites and/or apps that trigger the behavior you're seeing?

itv.com and github.com show the same behaviour.

@Picasso59 commented on GitHub (Apr 8, 2020): > @Picasso59 @jeffshead Can you provide some examples of websites and/or apps that trigger the behavior you're seeing? itv.com and github.com show the same behaviour.

GiteaMirror commented

2025-11-26 22:35:12 -06:00

@mpbw2 commented on GitHub (Apr 8, 2020):

@Picasso59 Thanks, I'm now seeing the intermittent toast message on itv.com (curiously only on a pixel 3, and only on itv.com - the others are fine, and all three are fine on a galaxy s10 running the same version of Chrome). Looking into it.

@mpbw2 commented on GitHub (Apr 8, 2020): @Picasso59 Thanks, I'm now seeing the intermittent toast message on itv.com (curiously only on a pixel 3, and only on itv.com - the others are fine, and all three are fine on a galaxy s10 running the same version of Chrome). Looking into it.

GiteaMirror commented

@tomo92s commented on GitHub (Apr 8, 2020):

Can someone explain why version 2.2.8 displays the icon on notification bar correctly and version 2.3.1 no longer? Redmi Note 4X

@tomo92s commented on GitHub (Apr 8, 2020): Can someone explain why version 2.2.8 displays the icon on notification bar correctly and version 2.3.1 no longer? Redmi Note 4X

GiteaMirror commented

2025-11-26 22:35:12 -06:00

@Picasso59 commented on GitHub (Apr 8, 2020):

@Picasso59 Thanks, I'm now seeing the intermittent toast message on itv.com (curiously only on a pixel 3, and only on itv.com - the others are fine, and all three are fine on a galaxy s10 running the same version of Chrome). Looking into it.

FYI I'm using OnePlus 6T (Android 10, most recent firmware) and Chrome 80.0.3987.162 (most recent). There are times the warning show for a few seconds, then disappears. At other times it shows briefly, but is flashing during that time.

@Picasso59 commented on GitHub (Apr 8, 2020): > @Picasso59 Thanks, I'm now seeing the intermittent toast message on itv.com (curiously only on a pixel 3, and only on itv.com - the others are fine, and all three are fine on a galaxy s10 running the same version of Chrome). Looking into it. FYI I'm using OnePlus 6T (Android 10, most recent firmware) and Chrome 80.0.3987.162 (most recent). There are times the warning show for a few seconds, then disappears. At other times it shows briefly, but is flashing during that time.

GiteaMirror commented

2025-11-26 22:35:12 -06:00

@jeffshead commented on GitHub (Apr 8, 2020):

The username and password are filled when using a desktop. Only the
username gets filled on Android:

https://www.righteverywhere.com

Is there a way to provide a URL, privately? The web page I would like to
share with you is not indexed and I'd like to keep it that way.

On Wed, Apr 8, 2020, 9:51 AM Matt Portune notifications@github.com wrote:

@Picasso59 https://github.com/Picasso59 @jeffshead
https://github.com/jeffshead Can you provide some examples of websites
and/or apps that trigger the behavior you're seeing?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bitwarden/mobile/issues/784#issuecomment-610972250,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACVLU7OG32QWTYVRQAVSS3RLR6NPANCNFSM4LO75HAA
.

@jeffshead commented on GitHub (Apr 8, 2020): The username and password are filled when using a desktop. Only the username gets filled on Android: https://www.righteverywhere.com Is there a way to provide a URL, privately? The web page I would like to share with you is not indexed and I'd like to keep it that way. On Wed, Apr 8, 2020, 9:51 AM Matt Portune <notifications@github.com> wrote: > @Picasso59 <https://github.com/Picasso59> @jeffshead > <https://github.com/jeffshead> Can you provide some examples of websites > and/or apps that trigger the behavior you're seeing? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/bitwarden/mobile/issues/784#issuecomment-610972250>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AACVLU7OG32QWTYVRQAVSS3RLR6NPANCNFSM4LO75HAA> > . >

GiteaMirror commented

@mpbw2 commented on GitHub (Apr 9, 2020):

@Picasso59 @jeffshead Here's another build to try. Let me know if this improves anything for you.

[Edit: link removed, latest Google Play beta contains fixes]

@jeffshead If this still isn't working I'll find a way for you to PM me a URL.

@mpbw2 commented on GitHub (Apr 9, 2020): @Picasso59 @jeffshead Here's another build to try. Let me know if this improves anything for you. [Edit: link removed, latest Google Play beta contains fixes] @jeffshead If this still isn't working I'll find a way for you to PM me a URL.

GiteaMirror commented

@Picasso59 commented on GitHub (Apr 9, 2020):

@Picasso59 @jeffshead Here's another build to try. Let me know if this improves anything for you.

I've hammered a few logins and it seems to be working well. After installation, I cleared the storage and cache, followed by restarting the phone. Auto-fill service: enabled. Overlay permission: granted. Auto-fill accessibility service: off. If I enable the accessibility service I see the BW warning again, but it works fine without it.

@Picasso59 commented on GitHub (Apr 9, 2020): > @Picasso59 @jeffshead Here's another build to try. Let me know if this improves anything for you. I've hammered a few logins and it seems to be working well. After installation, I cleared the storage and cache, followed by restarting the phone. Auto-fill service: enabled. Overlay permission: granted. Auto-fill accessibility service: off. If I enable the accessibility service I see the BW warning again, but it works fine without it.

GiteaMirror commented

@Snuupy commented on GitHub (Apr 12, 2020):

On my Redmi Note 4X with Android 7.0 notification still not appearing.

The quick settings tile isn't a notification, it's a tile that you have to enable it via the quick settings panel.
Google led me here for the Redmi Note 4X:

gadgetdetail.com/xiaomi-redmi-note-4-change-quick-toggles-notification-bar

@mportune-bw This tile does not autofill/read the app bundle. It only opens "My Vault".

@Snuupy commented on GitHub (Apr 12, 2020): > > On my Redmi Note 4X with Android 7.0 notification still not appearing. > > The quick settings tile isn't a notification, it's a tile that you have to enable it via the quick settings panel. > Google led me here for the Redmi Note 4X: > > [gadgetdetail.com/xiaomi-redmi-note-4-change-quick-toggles-notification-bar](https://www.gadgetdetail.com/xiaomi-redmi-note-4-change-quick-toggles-notification-bar/) @mportune-bw This tile does not autofill/read the app bundle. It only opens "My Vault".

GiteaMirror commented

@mpbw2 commented on GitHub (Apr 12, 2020):

@Snuupy There's a third tile labeled "Auto-fill" in the most recent version linked above. Once enabled it performs the same function that the notification used to.

@mpbw2 commented on GitHub (Apr 12, 2020): @Snuupy There's a third tile labeled "Auto-fill" in the most recent version linked above. Once enabled it performs the same function that the notification used to.

GiteaMirror commented

@Snuupy commented on GitHub (Apr 15, 2020):

@mportune-bw I believe I have run into a syncing bug specifically when there are more than 42717 lines of JSON in the database file. I have reproduced this on 2 separate servers (Bitwarden official + bitwarden_rs that I self-host, bw_rs is NOT the problem) and on 3 bitwarden android versions: 2.2.8 (2136), 2.3.1 (2257), and 2.3.1 (2299)

The results are as follows:
2136: syncs with both servers with database export files > 42717 lines long
2257: syncs with both servers with database export files > 42717 lines long
2299: fails on databases > 42717 lines long (at least for my database)
The error received is: "Syncing failed".

Downgrading (obviously) fixes this problem, but does not allow me to use the quick settings tile to auto-fill my logins.

I originally thought it was my database that was corrupted, but any combination of my logins (as long as < 42717 lines long) works. The second I add 1 more login such that it is longer than 42717 lines, it gives me a syncing error. I have spent several hours debugging this and am happy to provide logs if you can direct me to instructions that tell me how to provide them. At this point, I believe the bug is with the android client and not the server.

@Snuupy commented on GitHub (Apr 15, 2020): @mportune-bw I believe I have run into a syncing bug specifically when there are more than 42717 lines of JSON in the database file. I have reproduced this on 2 separate servers (Bitwarden official + bitwarden_rs that I self-host, bw_rs is NOT the problem) and on 3 bitwarden android versions: 2.2.8 (2136), 2.3.1 (2257), and 2.3.1 (2299) The results are as follows: 2136: syncs with both servers with database export files > 42717 lines long 2257: syncs with both servers with database export files > 42717 lines long 2299: fails on databases > 42717 lines long (at least for my database) The error received is: "Syncing failed". Downgrading (obviously) fixes this problem, but does not allow me to use the quick settings tile to auto-fill my logins. I originally thought it was my database that was corrupted, but any combination of my logins (as long as < 42717 lines long) works. The second I add 1 more login such that it is longer than 42717 lines, it gives me a syncing error. I have spent several hours debugging this and am happy to provide logs if you can direct me to instructions that tell me how to provide them. At this point, I believe the bug is with the android client and not the server.

GiteaMirror commented

@dextersnp commented on GitHub (Apr 15, 2020):

@Picasso59 @jeffshead Here's another build to try. Let me know if this improves anything for you.

[Edit: link removed, latest Google Play beta contains fixes]

@jeffshead If this still isn't working I'll find a way for you to PM me a URL.

Apparently solved for me, I will continue testing, tks!

@dextersnp commented on GitHub (Apr 15, 2020): > @Picasso59 @jeffshead Here's another build to try. Let me know if this improves anything for you. > > [Edit: link removed, latest Google Play beta contains fixes] > > @jeffshead If this still isn't working I'll find a way for you to PM me a URL. Apparently solved for me, I will continue testing, tks!

GiteaMirror commented

@mpbw2 commented on GitHub (Apr 24, 2020):

The Google Play beta has been updated with the latest accessibility/autofill fixes (build 2353).

@mpbw2 commented on GitHub (Apr 24, 2020): The Google Play beta has been updated with the latest accessibility/autofill fixes (build 2353).

GiteaMirror commented

2025-11-26 22:35:15 -06:00

@nkm8 commented on GitHub (Apr 24, 2020):

I tried the latest beta (2.3.1) on a Pixel 3 (Android 10) and I am still seeing issues. Specifically, http://www.costco.com is consistently reproduceable when trying to log in. STR:

Focus password field (no BW prompt)
Change input focus to different field, then back to password field (no BW prompt - sometimes this works on other sites)
Try new 'Auto-fill' BW quick-setting tile
BW opens, prompts for fingerprint
BW main screen opens and displays toast message "no password fields detected"
I can manually search and copy my password here, but this is annoying
Tap back button to navigate back to costco.com in Chrome
Focus in/out of password field and BW will correctly show a matching account and auto-fill user/pass

@nkm8 commented on GitHub (Apr 24, 2020): I tried the latest beta (2.3.1) on a Pixel 3 (Android 10) and I am still seeing issues. Specifically, http://www.costco.com is consistently reproduceable when trying to log in. STR: - Focus password field (no BW prompt) - Change input focus to different field, then back to password field (no BW prompt - sometimes this works on other sites) - Try new 'Auto-fill' BW quick-setting tile - BW opens, prompts for fingerprint - BW main screen opens and displays toast message "no password fields detected" - I can manually search and copy my password here, but this is annoying - Tap back button to navigate back to costco.com in Chrome - Focus in/out of password field and BW will correctly show a matching account and auto-fill user/pass

GiteaMirror commented

@nkm8 commented on GitHub (Apr 24, 2020):

Alternative work-around:

When you focus the password field in Chrome, a key icon is displayed in the bottom left corner to open the Chrome saved passwords feature
Click the key - Chrome displays "no saved passwords for www.costco.com"
Click the password field again and BW displays the "Auto-fill with Bitwarden - go to my vault" prompt

I will add, this work-around isn't ideal, either, because BW displays that prompt even if BW is already unlocked. If you focus/re-focus the password field a 3rd time, BW displays both the matching account (correct) and the "go to my vault" prompt (not sure if this is correct or not)

@nkm8 commented on GitHub (Apr 24, 2020): Alternative work-around: - When you focus the password field in Chrome, a key icon is displayed in the bottom left corner to open the Chrome saved passwords feature - Click the key - Chrome displays "no saved passwords for www.costco.com" - Click the password field again and BW displays the "Auto-fill with Bitwarden - go to my vault" prompt I will add, this work-around isn't ideal, either, because BW displays that prompt even if BW is already unlocked. If you focus/re-focus the password field a 3rd time, BW displays both the matching account (correct) and the "go to my vault" prompt (not sure if this is correct or not)

GiteaMirror commented

2025-11-26 22:35:15 -06:00

@mpbw2 commented on GitHub (Apr 24, 2020):

@nkm8 Are you using build 2353 with both accessibility & autofill service enabled? I'm not experiencing any issues with www.costco.com using Chrome on a Pixel 3.

@mpbw2 commented on GitHub (Apr 24, 2020): @nkm8 Are you using build 2353 with both accessibility & autofill service enabled? I'm not experiencing any issues with `www.costco.com` using Chrome on a Pixel 3.

GiteaMirror commented

2025-11-26 22:35:15 -06:00

@nkm8 commented on GitHub (Apr 24, 2020):

@mportune-bw Confirmed version is build 2353, auto-fill service and auto-fill accessibility service both enabled:
Chrome version: 81.0.4044.117
Android build: QQ2A.200405.005

Not sure what other details would be useful.

@nkm8 commented on GitHub (Apr 24, 2020): @mportune-bw Confirmed version is build 2353, auto-fill service and auto-fill accessibility service both enabled: Chrome version: 81.0.4044.117 Android build: QQ2A.200405.005 Not sure what other details would be useful.

GiteaMirror commented

2025-11-26 22:35:16 -06:00

@mpbw2 commented on GitHub (Apr 24, 2020):

@nkm8 We have an identical configuration. Have you disabled Chrome's built-in password manager?

@mpbw2 commented on GitHub (Apr 24, 2020): @nkm8 We have an identical configuration. Have you disabled Chrome's built-in password manager?

GiteaMirror commented

2025-11-26 22:35:16 -06:00

@tomo92s commented on GitHub (Apr 24, 2020):

Why still old option not working? It was better that way...

@tomo92s commented on GitHub (Apr 24, 2020): Why still old option not working? It was better that way... ![Screenshot_2020-04-24-15-56-07-372_com android chrome](https://user-images.githubusercontent.com/32452522/80220637-6ba38c80-8644-11ea-9688-99943b096a91.jpg)

GiteaMirror commented

2025-11-26 22:35:17 -06:00

@mpbw2 commented on GitHub (Apr 24, 2020):

@tomo92s The way the notification worked was not battery-friendly. The Auto-fill quick-settings tile provides the same functionality without the power consumption.

@mpbw2 commented on GitHub (Apr 24, 2020): @tomo92s The way the notification worked was not battery-friendly. The Auto-fill quick-settings tile provides the same functionality without the power consumption.

GiteaMirror commented

2025-11-26 22:35:17 -06:00

@tomo92s commented on GitHub (Apr 24, 2020):

@mportune-bw Maybe you will do two versions of filling? Please...

@tomo92s commented on GitHub (Apr 24, 2020): @mportune-bw Maybe you will do two versions of filling? Please...

GiteaMirror commented

2025-11-26 22:35:18 -06:00

@nkm8 commented on GitHub (Apr 24, 2020):

@mportune-bw Is it possible to completely disable Chrome's password manager?
Chrome settings -> Passwords

'save passwords' is off
'auto sign-in' is unchecked

@nkm8 commented on GitHub (Apr 24, 2020): @mportune-bw Is it possible to completely disable Chrome's password manager? Chrome settings -> Passwords - 'save passwords' is off - 'auto sign-in' is unchecked

GiteaMirror commented

2025-11-26 22:35:18 -06:00

@mpbw2 commented on GitHub (Apr 24, 2020):

@nkm8 Any chance there is another accessibility app installed and enabled? (Android settings -> Accessibility -> Downloaded Services)

@mpbw2 commented on GitHub (Apr 24, 2020): @nkm8 Any chance there is another accessibility app installed and enabled? (Android settings -> Accessibility -> Downloaded Services)

GiteaMirror commented

2025-11-26 22:35:18 -06:00

@nkm8 commented on GitHub (Apr 24, 2020):

@mportune-bw "My Verizon Guided Navigation" and "Tasker" - neither are enabled.

@nkm8 commented on GitHub (Apr 24, 2020): @mportune-bw "My Verizon Guided Navigation" and "Tasker" - neither are enabled.

GiteaMirror commented

2025-11-26 22:35:19 -06:00

@jeffshead commented on GitHub (Apr 24, 2020):

I just tried the latest beta (2353). I see no improvement on my Pixel XL with Firefox. In fact, (maybe coincidence) I am now getting a lot of the "There are no items in your vault for x.com" warnings when I touch the Auto-fill with Bitwarden pop-up. If I simply touch the back button and try again, it finds the correct login. Seems to happen mainly when I start with the Bitwarden app being in a locked state. Subsequent attempts work if the Bitwarden app was previously unlocked. This also happens on a Galaxy S7.

Has anyone tried or had success in having BW on an Android device auto-fill the login form on:
https://www.righteverywhere.com/
Works fine on Windows.

@jeffshead commented on GitHub (Apr 24, 2020): I just tried the latest beta (2353). I see no improvement on my Pixel XL with Firefox. In fact, (maybe coincidence) I am now getting a lot of the _"There are no items in your vault for x.com"_ warnings when I touch the _**Auto-fill with Bitwarden**_ pop-up. If I simply touch the back button and try again, it finds the correct login. Seems to happen mainly when I start with the Bitwarden app being in a locked state. Subsequent attempts work if the Bitwarden app was previously unlocked. This also happens on a Galaxy S7. Has anyone tried or had success in having BW on an Android device auto-fill the login form on: https://www.righteverywhere.com/ Works fine on Windows.

GiteaMirror commented

2025-11-26 22:35:19 -06:00

@bayasdev commented on GitHub (Apr 24, 2020):

I just tried the latest beta (2353). I see no improvement on my Pixel XL with Firefox. In fact, (maybe coincidence) I am now getting a lot of the "There are no items in your vault for x.com" warnings when I touch the Auto-fill with Bitwarden pop-up. If I simply touch the back button and try again, it finds the correct login. Seems to happen mainly when I start with the Bitwarden app being in a locked state. Subsequent attempts work if the Bitwarden app was previously unlocked.

Has anyone tried or had success in having BW on an Android device auto-fill the login form on:
https://www.righteverywhere.com/
Works fine on Windows.

It's working for me on Vivaldi Snapshot and FF Nightly with latest BW Play Store beta

@bayasdev commented on GitHub (Apr 24, 2020): > I just tried the latest beta (2353). I see no improvement on my Pixel XL with Firefox. In fact, (maybe coincidence) I am now getting a lot of the _"There are no items in your vault for x.com"_ warnings when I touch the _**Auto-fill with Bitwarden**_ pop-up. If I simply touch the back button and try again, it finds the correct login. Seems to happen mainly when I start with the Bitwarden app being in a locked state. Subsequent attempts work if the Bitwarden app was previously unlocked. > > Has anyone tried or had success in having BW on an Android device auto-fill the login form on: > https://www.righteverywhere.com/ > Works fine on Windows. It's working for me on Vivaldi Snapshot and FF Nightly with latest BW Play Store beta ![Screenshot_20200424-093759_Vivaldi](https://user-images.githubusercontent.com/49411169/80224669-9f17f400-860f-11ea-9075-d40910992987.jpg)

GiteaMirror commented

2025-11-26 22:35:19 -06:00

@jeffshead commented on GitHub (Apr 24, 2020):

It's working for me on Vivaldi Snapshot and FF Nightly with latest BW Play Store beta

Did you actually create login credentials in BW and see if it will fill in the username and password fields on that page?

@jeffshead commented on GitHub (Apr 24, 2020): > It's working for me on Vivaldi Snapshot and FF Nightly with latest BW Play Store beta Did you actually create login credentials in BW and see if it will fill in the username and password fields on that page?

GiteaMirror commented

2025-11-26 22:35:20 -06:00

@bayasdev commented on GitHub (Apr 24, 2020):

It's working for me on Vivaldi Snapshot and FF Nightly with latest BW Play Store beta

Did you actually create login credentials in BW and see if it will fill in the username and password fields on that page?

Yes, I created a fake entry previously for this specific website.

Edit: I forgot to say that I explicitly disabled battery optimizations for BW app, enabled autofill API and accessibility service.

@bayasdev commented on GitHub (Apr 24, 2020): > > It's working for me on Vivaldi Snapshot and FF Nightly with latest BW Play Store beta > > Did you actually create login credentials in BW and see if it will fill in the username and password fields on that page? Yes, I created a fake entry previously for this specific website. Edit: I forgot to say that I explicitly disabled battery optimizations for BW app, enabled autofill API and accessibility service. ![Screenshot_20200424-101027_Vivaldi](https://user-images.githubusercontent.com/49411169/80227915-f91ab880-8613-11ea-9178-65c91da80ebd.jpg)

GiteaMirror commented

2025-11-26 22:35:20 -06:00

@jeffshead commented on GitHub (Apr 24, 2020):

Did you actually create login credentials in BW and see if it will fill in the username and password fields on that page?
Yes, I created a fake entry previously for this specific website.

Edit: I forgot to say that I explicitly disabled battery optimizations for BW app, enabled autofill API and accessibility service.

Thanks for the followup. Doesn't work for me. I installed Vivaldi Snapshot on a Pixel XL and a Galaxy S7. Both have disabled battery optimizations for BW app and auto-fill & accessibility service enabled.

With Firefox nightly, BW says, "No password fields detected".

@jeffshead commented on GitHub (Apr 24, 2020): > > Did you actually create login credentials in BW and see if it will fill in the username and password fields on that page? > Yes, I created a fake entry previously for this specific website. > > Edit: I forgot to say that I explicitly disabled battery optimizations for BW app, enabled autofill API and accessibility service. Thanks for the followup. Doesn't work for me. I installed Vivaldi Snapshot on a Pixel XL and a Galaxy S7. Both have disabled battery optimizations for BW app and auto-fill & accessibility service enabled. With Firefox nightly, BW says, _"No password fields detected"_.

GiteaMirror commented

@Tukks commented on GitHub (Apr 28, 2020):

Don't work either on last Firefox beta.
Everything in activated in autofill service.
When I close Firefox with a login page on and I re-open it, sometimes the bitwarden popup appear.
Bitwarden beta 2353.

@Tukks commented on GitHub (Apr 28, 2020): Don't work either on last Firefox beta. Everything in activated in autofill service. When I close Firefox with a login page on and I re-open it, sometimes the bitwarden popup appear. Bitwarden beta 2353.

GiteaMirror commented

@mpbw2 commented on GitHub (Apr 29, 2020):

Build 2376 is now available in the beta channel. Among other fixes, it hopefully stops the “BW needs your attention -- see auto-fill accessibility service…” popup from appearing on occasion even if you've already enabled the overlay permission.

Re: Firefox beta - it doesn't appear to be firing off any accessibility events, but regular autofill appears to be working. (Regular Firefox and Firefox Focus seem to work with both)

@mpbw2 commented on GitHub (Apr 29, 2020): Build 2376 is now available in the beta channel. Among other fixes, it hopefully stops the “BW needs your attention -- see auto-fill accessibility service…” popup from appearing on occasion even if you've already enabled the overlay permission. Re: Firefox beta - it doesn't appear to be firing off any accessibility events, but regular autofill appears to be working. (Regular Firefox and Firefox Focus seem to work with both)

GiteaMirror commented

@Stephan-P commented on GitHub (Apr 30, 2020):

Beta version: 2.3.1 (2376) is giving me a nice pop up overlay to tap.

Nokia 3.1, Android 9
Vivaldi and Edge browsers
Accessibility service on, Autofill service off
URL matching option: any

@Stephan-P commented on GitHub (Apr 30, 2020): Beta version: 2.3.1 (2376) is giving me a nice pop up overlay to tap. - Nokia 3.1, Android 9 - Vivaldi and Edge browsers - Accessibility service on, Autofill service off - URL matching option: any

GiteaMirror commented