Autofill and context menu stopped working.

[JABirchall]

Steps To Reproduce

Unknown how to reproduce, they just stopped working.

Expected Result

expect to see autofill options in context menu and autofill from the extention to work.

Actual Result

Bitwarden context menu has disapeared. Clicking on login in the extention results in "unable to autofill the item" error.

Screenshots or Videos

Additional Context

Disabling and reenabling the extention fixes the issue untill the browser is restarted.

Operating System

Windows

Operating System Version

19045.4780

Web Browser

Firefox

Browser Version

129.0.2

Build Version

2024.8.*, 2024.9.*

Issue Tracking Info

• [X] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[gemal]

console says Error: Could not establish connection. Receiving end does not exist. trigger-autofill-script-injection.js:5:20

[JABirchall]

console says Error: Could not establish connection. Receiving end does not exist. trigger-autofill-script-injection.js:5:20

Yes it does.

[Krychaz]

Hello,

Will you try uninstalling the application, removing any leftover data, powering off and on your device and re-installing? Does this issue still persist?

Guide to the leftover data: https://bitwarden.com/help/data-storage/#on-your-local-machine

Let me know if that helps.

[budimanjojo]

@Krychaz It's not fixing the problem for me. I also found out that this problem is happening because of weird login issue. When I first start Firefox, Bitwardent client is not showing the padlock icon but still ask me to unlock my vault. And if I unlock my vault, autofill will not work. And I also can't log out of the vault.

But, if I go to Add-ons Manager, disable and re enable the Bitwarden extension, then the extension will then show padlock and when I unlock the vault autofill will then work again.

This is happening after the recent update (version 2024.8.1 updated on 31st August 2024).

[Bbawt]

Bitwarden browser extension (Edge on Win 10) stopped autofilling today and logged me out each time I closed my browser even though I had set it to Never. Yesterday I installed the android app and authenticator on my phone. I just uninstalled the android apps and the browser extension is back to working properly - autofilling and not logging me out.

[reikrom]

Autofill stopped working on Chrome, when opening the Extension floating window it was stuck in the loading icon state. After a while, it loaded vault content but autofill still didn't work.

Fix that worked:

1. Remove extension from chrome
2. Add the extension back to Chrome.
3. Re-bind autofil hotkey in settings - Autofill the last used login for the current website

[ChrisLane]

Yep, removing the extension and then re-adding it fixed the issue for me in Firefox on Linux.

[Danie10]

Removing the extension and then re-adding it in Brave on Linux did not work for me. It just broke too on my Vivaldi browser when the extension updated to v2024.8.1. It's a problem as every login I have is inside Bitwarden.

EDIT: Reinstalling on Vivaldi browser appears to be working.

[Danie10]

Now working on Brave Beta for me from today - deleted the extension again, and reinstalled, and noted the extension version matches the server version.

[Bbawt]

Update: Mine started working again instantly after I deleted my BW app on my phone. Yesterday, the extension on Edge quit working again. Had to uninstall the extension and re-add to Edge and it works again. I can't tell if this is an open bug or not.

[Err0rFlynnn]

this happened to me after updating to Nightly 132.0a1 (2024-09-06)

[JABirchall]

Hello,

Will you try uninstalling the application, removing any leftover data, powering off and on your device and re-installing? Does this issue still persist?

Guide to the leftover data: https://bitwarden.com/help/data-storage/#on-your-local-machine

Let me know if that helps.

This only fixes it until the browser is restarted, then its broken again.

HOWEVER: I did notice there is a new UI for the dropdown on login fields.

This is new, it didnt look like this before it all broke. So from process of deduction, whatever changes that new dropdown UI is responsable for the breaking.

[Danie10]

Mine has stopped again on Brave Stable on Manjaro Linux after I logged in the next day. Autofill stopped, vault not syncing. It says it last synced yesterday evening. This is after I again removed the extension and its data folder yesterday, and re-installed it.

[budimanjojo]

Like I said above, signing in / unlock the vault from cold start is not working unless the extension is being toggled off and on. It's very frustrating.

[Danie10]

More frustrating is Bitwarden not acknowledging the issue here and assigning the issue to someone.

I'm using the Extensity extension to just toggle it off and on again, and then it seems to work until I reboot. This is at least the easiest way to toggle. I did say to Bitwarden in the issue I logged to the call centre, that considering the information I gave and the reference to this Github issue, that I really did not appreciate the "standard form response" I got to the issue I logged. Clearly no-one even wrote what I had stated I'd already tried, nor even looked at this Github issue.

I'm a paying premium member, and would at least like to have seen more involvement and presence, seeing this affects so many people.

[pyluyten]

Had same issue on Chrome/Linux

• Autofill did not work ( I could copy paste login then password)
• Log off did not work

Removed and reinstalled extension fixed it.

Extension - 2024.8.1 Chrome - Version 128.0.6613.119 (Build officiel) (64 bits)

[rpodric]

Does 2024.8.2 make a difference? Not that the brief release notes for it mention anything seemingly related.

Also, clearly not everyone is seeing the issue or it would have been much more widely discussed by now. It might be informative to learn why this is the case.

[budimanjojo]

@pyluyten Have you tried rebooting your computer? For me and many people here, after a reboot (even browser restart on me) will trigger the issue again and I needed to disable and reenable the extension again.

[pyluyten]

@budimanjojo oh sadly you are right. Browser restart was fine but after full reboot then issues are back, some ui freezes + impossible to autofill.

Both my Linux are under Wayland

[Bbawt]

I had interesting discoveries yesterday after on and off again issues with the "unable to autofill" notice. Win 10 Edge BW extension opens from fresh boot in either locked status (even though my setting for vault timeout is "never") or unlocked but I get the orange unable to fill bar. If its unlocked yet unable to fill, I then go and boot up my Win 11 laptop Edge and BW extension works just fine - and when that happens, BW extension on Win 10 Edge starts working normally again on its own.

I also had a similar situation just on the Win 10 computer - today after boot Edge BW extension says "locked". Switch immediately to Vivaldi browser and BW extension is working fine. Switch back to Win 10 Edge and extension is unlocked and working fine.

No difference in browser versions, extension versions, or other extensions.

[rpodric]

@Bbawt Wow, that is beyond odd, especially since in at least one case you found that an action on one device seemed to affect another. That suggests that BW has some kind of IP-based system in which if it sees you logged in successfully from that IP, at least for a period of time it'll then relax things for you. I wasn't aware that was a feature.

[Bbawt]

@rpodric yes, very odd. In discussion with one of the BW moderators on reddit yesterday I was wondering if it might be related to sync issues somehow, especially since I don't have to do anything to either unlock or fix the autofill on Win 10 Edge except start it through a different browser. But there is no consistent pattern on the Win 10 Edge version - after boot it will either start in a Locked status (that's getting more common even though setting are set to never lock), or an unlocked status but unable to autofill, or sometimes (although more rare now), it opens in full proper working status. I can't find a common pattern.

[jnihil]

@rpodric I am also seeing this issue for the past couple of weeks on Brave (Flatpak). I recover via remove/reinstall of the extension, but the problem returns after some interval. I do not see this issue on Floorp browser (.deb). Both browsers are used actively and on the same Debian 12 system.

EDIT: I closed/reopened Floorp a week after this post and it is also not working, so both Brave/Floorp on Debian-12/XFCE is no good.

[Danie10]

Now I'm really worried as I had to add a new password last night. This morning, Bitwarden extension says it is not syncing to vault after I logged in. If I delete and reinstall the extension (like I'm now doing daily), will I lose that password I added yesterday? This is all seems to be falling apart for me.

For me, it has been a combination of autofill as well as vault syncing stopping.

EDIT: OK just noticed that although the extension says sync failed and shows yesterday's date, if I go back to sync about 5 mins later, it actually shows the current date and time. Verified in another browser that the password updated (even tho that extension also says vault sync failed).

[JABirchall]

Now I'm really worried as I had to add a new password last night. This morning, Bitwarden extension says it is not syncing to vault after I logged in. If I delete and reinstall the extension (like I'm now doing daily), will I lose that password I added yesterday? This is all seems to be falling apart for me.

For me, it has been a combination of autofill as well as vault syncing stopping.

EDIT: OK just noticed that although the extension says sync failed and shows yesterday's date, if I go back to sync about 5 mins later, it actually shows the current date and time. Verified in another browser that the password updated (even tho that extension also says vault sync failed).

Ive already started doing daily exports incase the day comes that the sync doesnt happen and i loss an important password.

But this issue seriously needs to be addressed.

[arnelap]

Since it works if you turn off and on the extension I'm thinking "something that takes time to initiate within the browser on first browser start"

What are you-all's DNS settings in Firefox?/

I had it on "'Max Protection" and just switched in to "Default" and the last few restarts Bitwarden worked without having to restart the extension or the browser!

But I have had other cases where suddenly it seemed to work for a bit, so it's difficult to debug this issue. Anyone care to test the same?

[ccalhoun1999]

I'm on default protection for DNS (although using Zen-browser, a derivative of Firefox so things may be different) but the problem still occurs for me.

[budimanjojo]

I have DNS protection set to "Off" this entire time because I use my own DNS server so that's definitely not the real culprit.

[Bbawt]

Since it works if you turn off and on the extension I'm thinking "something that takes time to initiate within the browser on first browser start"

I think so too, and I'm wondering if on that first browser start that the issue of being logged out or getting the Unable to autofill is a result of that initiation gone wrong. I now know if I open my browser on boot, BW extension (2024.8.2) shows me locked out even though I have it set to never. Stays that way as long as the browser is open and no other browser used that has BW. Close the browser and restart it, and BW opens up working just fine. So my work around seems to be - open browser, close browser, open again.

[ccalhoun1999]

I'm unsure if its related, but my vault is not locking either even with a vault timeout set.

[budimanjojo]

Seems like the latest version 2024.8.2 fixes this issue.

EDIT: No the problem persists even after 2024.8.2

[JABirchall]

preliminary results, 2024.8.2 fixes the issue. will give it a couple day to see if it regresses back to broken.

[Danie10]

Mine has just updated to version 2024.9.0 today so let's see how this goes.

[TiMcCall]

I can recreate this issue with my firefox browser after a hard reboot (holding down my computers power button) It no longer fills in the fields. To resolve the issue I had to reboot from the windows menu. I was able to repeat it several times with the same results.

[JABirchall]

I can recreate this issue with my firefox browser after a hard reboot (holding down my computers power button) It no longer fills in the fields. To resolve the issue I had to reboot from the windows menu. I was able to repeat it several times with the same results.

Then dont do that.

[rpodric]

2024.9.0 is certainly promising. It was a surprise seeing that get into the Chrome store so quickly given that it just hit GitHub yesterday. Only listed fix is "bug fixes" but so far so good upon two launches anyway. I've never had it work with two successive launches since the problem began.

[Danie10]

Sadly for me v2.9.0 is still doing the same on Brave and Vivaldi browsers. Nearly a minute to login, and subsequent vault syncs fail, as well as autofill. I did delete and reinstall v2.9.0 yesterday on my Brave browser.

The question is whether Bitwaaden actually is aware of this at all? I did log the issue to their call centre, but I'm not aware if anyone from their team has accepted or allocated this issue yet? Right now I'm using Proton Pass to be sure (after just paying for another year of Bitwarden) so this is getting messy as I don't know whether to trust my Bitwarden account when I see vault sync failed.

All my other extensions, inc Proton Pass, appear to be working as normal. My Bitwarden is set to lock on browser restart, so I always start in a locked out status.

[rpodric]

You're sure that you're giving it enough time? Today I thought it wasn't working, since a minute or even a little more after launching the browser (note that I have several tabs opening automatically, which slows things down) the extension still wasn't ready. But then a minute or so later I noticed that it was ready. So, while it may not be as fast as before, it doesn't seem to have the recent problem.

[Bbawt]

2024.9.0. Open Edge, extension shows not logged in and asks for master password to unlock. Leave browser open for more than an hour, no change. Close browser and reopen and extension is ready within about 2 sec. No more "unable to autofill" - that seems to be fixed, but the inability to be unlocked with first open remains for me. Does not happen on Vivaldi browser.

[Danie10]

On Edge after I log into Bitwarden extension, the icon still shows the padlock symbol. I'm wondering if this is not related to the auto-lock after an hour or something similar. Because if I just log in in then autofill and vault sync works. A while after that it stops.

Thing is, it is still broke across all my browsers even after re-installing the extension. I can't believe it can go so wrong. But it is a major pain to have to reinstall every day across 4 different browsers. I'm testing one browser now to never lock and see what happens.

[rpodric]

I was fooled with 2024.9.0, as it doesn't work consistently. This is an improvement on the 8.1 release, which consistently doesn't work (without the off/on toggle) on those systems where that was needed at all (some people never see a problem with any of these releases).

With 9.0, when you do have the problem, the extension can look normal (i.e. when clicked you see your logins and no sign of any issue) but autofill doesn't work using any method without toggling off/on first. So, appearances can be deceiving.

[Danie10]

Not sure if this will help, but I did turn on Error Collection for the extension and this is one that seems to repeat quite a bit (bearing in mind I have deleted the extension folder a few times and recreated it):

[lissyx]

I could not get autofill to work at all with 2024.8.1, then 2024.8.2 came and fixed it and now 2024.9.0 broke it again?

(edit: but somehow disabling/re-enabling the extension get it back working?)

[JABirchall]

Yea its still broken since the lastest updates. Updated the report adding 2024.9.0 is affected. @Krychaz any news on a fix? The extention is failing to do its primary purpose.

[Danie10]

@lissyx yes that has been deceptive to me as it works immediately after disabling (and even full delete and restore) and then it starts it issues after that again. It's driving me mad now, but I'm sick of every day reinstalling the extension across all three of my browsers (then changing each's settings, and using my Yubikey to reauthenticate). I've exported my data to Proton Pass and trying to use that until this is fixed - I just don't like the way Proton Pass works on the UI, so really would prefer to have a fully functioning Bitwarden extension.

Really don't know what else to try when the full deletion and reinstallation of the extension does not keep working.

[JABirchall]

Really don't know what else to try when the full deletion and reinstallation of the extension does not keep working.

You dont have to reinstall it, just disable and reenable the extension. It breaks against after the browser is restarted.

[123SONIC321]

This only fixes it until the browser is restarted, then its broken again.

I have the same exact issue I'm using Thorium | 126.0.6478.231 | win11 reinstalling the extension solved it until the browser is restarted

[Danie10]

Thanks @JABirchall yes the disable/enable is working now for me. Previous update was not doing so, so I started reinstalling. This is a bit better. Let's hope Bitwarden is aware of this issue and gets it fixed soon.

[rpodric]

I wouldn't hold your breath, since there's some X factor to this that may not be readily apparent. For example, on the same system with the same account, I have never reproduced the problem in Edge.

[jsspen]

Version: 2024.9.0 Server Version: 2024.9.0 Librewolf 130.0-3

I've been dealing with this for a while now. Disabling and re-enabling doesn't work reliably. Just had to do the reinstall again to get it working. Has there been any acknowledgement of this problem by the devs at Bitwarden?