No longer recognizing logins

I have been using Bitwarden for almost two years. Recently, on a number of web sites, after unlocking the vault, the browser extension does not appear to recognize and fill login forms.

For example, I go to www.pilotinstitute.com and select “login” from the home page. The login dialog is displayed in the web page and Bitwarden displays “+New login” as shown:


This suggests to me that the Bitwarden extension thinks this is a new login for which I do not have a vault entry saved. Ctrl-Shift-L does not autofill, right-clicking and choosing Bitwarden->Autofill login does not work.

The Bitwarden extension icon does not show any numbers which suggests that it doesn’t thing there is a vault entry that matches this site. I am using the default match detection. However, if I open the Bitwarden extension, it shows the vault entry for this site at the top:
Capture (2)

If I click on “Fill”, it correctly fills the username.

The same behavior occurs on a few other sites but it is inconstant. I think this is happening just after unlocking the vault.

Do you unlock your browser extension with a PIN? – Though it maybe doesn’t match a hundred percent, your issue mostly sounds like this one:

So, you might add your details to that GitHub issue, if you think it matches.

BTW, about which browser – and which extension version – are we talking?

Yes, that does sound like what I am experiencing.

Sorry, I forgot to add the version information.

Firefox 139.0.4
Bitwarden Version: 2025.5.0
SDK: ‘main (f28b4ef)’
Server version: 2025.6.2

Until this is fixed, the work-around is to click either a “launch” button () or a fill button within the browser extension pop-up window after you have first unlocked the extension. You should only need to do this once per unlock.

Isn’t that actually the same problem?

Probably not, since in that thread, the autofill keyboard shortcut still works.

I don’t want a workaround. Would rather see it fixed. :disappointed_face:

2 Likes

Are you saying that you are not going to log in to any of your accounts (using a work-around) until this is fixed?

You’re presenting a false dichotomy — no reasonable user or developer would not want to see this fixed, but most users would benefit from and appreciate a work-around to use while waiting for a fix to be developed, tested, and released.

1 Like

I had read that a workaround works and is therefore OK. I misunderstood it then, sorry for that.

1 Like