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

[qw4096]

The latest Android APP (2.3.1) cannot automatically fill in the account and password. Specifically, when the input box is clicked, the auto-fill window pops up quickly and disappears. There is no time to choose. Model is Huawei honor V20, system version Android 10

[Picasso59]

Having the same issue. Android 10, OnePlus 6T, using Chrome.

[Picasso59]

I've just updated to Chrome 80.0.3987.149 since my post a few minutes ago. It is working now!

[dkoppenh]

Left this on the community forum, but copying here: The latest update also broke the pop-up for me. Like others have reported, it appears for a split second and then disappears.

At least in the past, I could use the notification to autofill. LG V40 Android 9 Brave 1.5.9 based on Chrome 80.0.3987.132 Firefox 68.6

Interestingly, Chrome 80.0.3987.149 works

[Picasso59]

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.

[jeffshead]

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.

[THEOCKID]

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]

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]

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

[immanuelfodor]

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]

Here it is on sceen record.

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

[tomo92s]

Please restore old notification option

[guiggs]

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

[tomo92s]

I think is over...;/

[lfrancke]

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.

[MeiRos]

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

[immanuelfodor]

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

[tomo92s]

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

[thethomasboyer]

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.

[ghost]

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.

[mateusz-owczarek]

I have the same problem. Device info:

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

[MisteurZZ]

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

[Nyar233]

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

[tomo92s]

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

That not working. This is app issue

[bayasdev]

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

[superm1]

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.

[immanuelfodor]

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.

[Picasso59]

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.

[superm1]

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.

[mpbw2]

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]

[superm1]

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

[tomo92s]

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)

[ratenfanger]

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.

[Picasso59]

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.

[jeffshead]

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.

[mpbw2]

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?

[MisteurZZ]

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

[jeffshead]

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 .

[Picasso59]

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.

[mpbw2]

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.

[tomo92s]

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.

[mpbw2]

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/

[tomo92s]

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

[qw4096]

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

[mpbw2]

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

[Picasso59]

@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]

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

[mpbw2]

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

[tomo92s]

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

[Picasso59]

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

[jeffshead]

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 .