I am an Android user. Suddenly, I cannot use Bitwarden on any of my Galaxy Android devices anymore. It is not recognized in the Naver Whale browser whatsoever. How can I fix this?
I have enabled the autofill service and inline autofill option in the settings, as well as the accessibility service. I have also set Bitwarden as the default password service on Android.
My smartphone is a Galaxy S25 Ultra running Android 15 with One UI 7.0. I also use a Galaxy Tab, specifically the Galaxy Tab S9, running Android 14 with One UI 6.1.1. I am certain I was using the feature on my Galaxy Tab just a few days ago, but suddenly, it stopped working.
Chrome worked after applying the following solution. However, this cannot be applied to the Whale browser. The solution is as follows:
Go to: brave://flags
Search for âEnable the setting to provide a virtual view structure for Autofillâ and enable it with the option âenabled without any compatibility checkâ.
Restart the browser (itâs best to force quit).
A new menu should appear in settings below âDownloadsâ called âAutofill Servicesâ.
In that menu, select âother providersâ.
Restart the browser again.
EDIT:
The team is investigating reports of autofill issues, can you share more on which autofill settings you have enabled in the settings menu? Autofill service/inline/accessibility etc.
If you disable inline, does the overlay work?
Do you have âShow suggestion stripâ under âText correctionâ enabled in the gboard settings menu?
Have you tried reinstalling gboard?
Donât hesitate to contact support at Help Center | Bitwarden to provide additional detail.
I had inline autofill turned on and the popup stopped showing up. I turned off inline and everything worked againâŚ
However, previously I had these two options available to use at the same time. They werenât exclusive for me. I could have both the on-screen popup and the Inline showing. I donât remember how long ago it was, but it was that way for a few years until maybe this year.
There is no reason that this behaviour should have been changed.
These are two, separate options in the menu which can both be toggled on.
There is no help text indicating they are exclusive.
there is no visual signal e.g. Toggling one option on greys out the other.
They are often useful for different scenarios. For example, I have loads of logins to certain sites and inline is unclear, the popup is much easier.
The inline is faster for simple logins and creating new logins.
the popup box often detects fields that inline does not. But if I have inline turned on, the box never shows even if a field could be detected.
the user should be able to decide what combo suits them anyway.
This should be returned to its previous behaviour.
â there is no specific slider to activate the âoverlay/pop-upâ â but indeed, if âinlineâ is activated and it canât be shown, it should fall back to the âoverlayâ (âOtherwise, use the default overlay.â)
I think here (in the âafterâ video), we can see the next change: it can be chosen between âinlineâ and âpop-upâ â and Iâm not sure myself, if there still will be a fall back to âpop-upâ when one choses âinlineâ
Iâve been using SwiftKey since Iâve had bitwarden and I have never experienced this issue, so I donât think the problem lies with my chosen keyboard. Also changing keyboard doesnât change anything.
There are so many reports of the functionality having been changed that itâs clear an issue has been introduced. The fluidity with which bitwarden used to work has been noticeably interrupted.
The âOtherwiseâŚâ setting does not work at all. Thatâs part of the problem. The options now work exclusively. The inline option prevents the pop up box from showing entirely, even when inline does not work.
If itâs three months old, maybe it didnât work that way previous to three months ago? I thought it was a bug that would be fixed. It happens, but after months of the issue remaining I came here. I canât remember if it was the redesign or something else tbh.
What I know is that, previously, both settings could be turned on and displayed when necessary. Now itâs one or the other entirely.
EDIT: For me, the issue is something like this:
The inline prevents the default popup dialogue from showing.
When Inline doesnât work, it is meant to switch to default and/or accessibility, but doesnât.
The Bitwarden quick-tile action uses accessibility to work, but it uses the default popup which is being prevented by inline.
Previously, accessibility could override in line but it no longer can. Idk
I had that setting set already. I think there must have been some problem with the way the setting was applied. I changed it from another service to Google and then back to another service and now it works. I think thereâs a problem that causes this setting to appear to be set but not actually take effect.
Iâm having issues with this as well. Everything works as normal. Pops up , opens bitwarden, but nothing happens when I press the fill. Itâs like its not detecting the fields
What is your BW app version? (latest is 2025.8.1)
Did you set up those new settings: Important Android Autofill Updates ?
What browser are you using?
Do you have an innocuous example site, where we can try to reproduce?
Hi there, if the following isnât working for you:
Update to 2025.8.1 (rolling out now) and disable and reenable the toggles for âAutofill servicesâ (choose Bitwarden) and âChrome autofill integrationâ (choose other services), and restart your mobile browser.
Same problem here after updating to 2025.8.1. Login forms no longer offer auto-fill suggestions on either apps or websites. I have tried un-setting and re-setting Autofill Services, Ihave tried both Inline and Pop-up suggestion settings. Nothing works.
I am now forced to open the app, open Bitwarden, lookup the site, copy the username, switch back to the app, paste the username, switch back to Bitwarden, copy the password, switch back to the app, paste the password. Welcome back to 1998!
Just confirmed that this page is doing it. The fill pops up but nothing gets filled home
To be clear, it does fill once the actual login info shows up on the keyboard, but does not fill if you had to hit the bitwarden button and open bitwarden to select the login
@Xicor I just tested it and I could fill on the login form of https://ownyourfuture.vanguard.com/en/home/publogin with Vivaldi, Chrome and Firefox â Android 15, BW mobile app 2025.8.1.
I only experienced this once on that form, but I think that happened because my vault was locked in between (I use a very short interval on my mobile app).
