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

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

Have others tried side-loading the new version from the link above? I used the Chrome one on Brave Browser and it is working fine. That has certainly solved it for me with all my normal uBlock Origin etc on. Big thing was just to leave the unpacked extension files as they are, after installing it, otherwise the extension crashes. I'm on day 2 now and finally everything unlocked fine, vault syncing, and forms filling fine.

[msummers]

Chrome 129.0.6668.58 on Ubuntu 24.04 LTS with dist-chrome-MV3-251b8fc.zip from above has survived 3 browser restarts and continues to work well.

[LawrenceIRL]

Just confirming that so far using dist-firefox-b0f4b7b resolves the issue on my first machine here with Firefox v130.0.0 (RPM) on Fedora 40 x64 while on both X11 and Wayland.

[WrichikBasu]

dist-firefox-b0f4b7b works as intended on Firefox 130.0 on Ubuntu 22.04.4, x11.

[123SONIC321]

That could definitely help with diagnosing the issue, especially if you showed the results of the extension's background console log.

I will try to record once again when I get home

626427_movie.mp4

@cagonzalezcs

[colibris79]

dist-chrome-MV3-251b8fc.zip seems to be working fine as well with Chrome 129.0.6668.70 and Mint 21.3

[dovry]

Autofill stopped working again.
Bitwarden Version 2024.9.1
Firefox 130.0.1
Win 10 pro 22H2

disabling, re-enabling BW extension, and logging back in fixed it (temporarily? this happens a lot)

[Bbawt]

Desktop browser extension 2024.9.1 has been working fine for last 2 weeks on both Vivaldi and Edge. Vivaldi was open and BW working on desktop when I just installed Bitwarden on my ipad and logged in. Immediately my desktop browser extension logged out, and when I logged back in, it no longer autofills. This is the same issue I had several weeks ago when I installed BW app on my phone.

[tdewolff]

For me sometimes it works and sometimes it doesn't. Restarting the browser sometimes fixes it.

[thezoggy]

autofill stopped working

Bitwarden Version: 2024.9.1
Firefox: 130.0.1
OS: Win10 pro 22H2

restart browser and now it starts working again..

[Danie10]

My sideloaded version 2024.9.1 with Brave is still working perfectly. Logs in fine first time after browser start, and stays working for the rest of the day with autofill. I'm not sure whether the app store version 2024.9.1 is out yet.

[123SONIC321]

Idk why but nothing changed for me after updating (it's been 3 days)

Bitwarden Version: 2024.9.1
Thorium: 126.0.6478.231 (Official Build) (64-bit)
OS: Win11 24H2 Pro

[JasonKhew96]

please read this #10814 (comment) before commenting, stop pinging everyone subscribed to this issue if you don't have new information. Thank you.

[cagonzalezcs]

To that effect, given that the work for that PR seems to resolve this issue for those who have side-loaded the fix, I'll be closing this thread as completed.

Those changes should be release with the next version of the extension, until then if the issue persists you can fix the problem by reloading the extension or if you'd like you can side-load the extension artifacts that I linked previously until the next release.

Also, just want to re-iterate a huge thank you to everyone who tested the fix.

[stateless]

I have this problem, which has been closed and pointed at this issue.

Autofill works, but the context menu function ignores the setting option. So I can't turn the field context popup off. Also ignores the "excluded domains list" option.

[JABirchall]

Any timeline when the update will be released @cagonzalezcs

[Gudine]

It's been working for me since v2024.10.0.

[tayl]

Any timeline when the update will be released @cagonzalezcs

It's been working for me since v2024.10.0.

This build is not released widely yet. Still moving through the bureaucracy of various app/extension stores.

[stateless]

Just updated for Firefox on Linux to v2024.10.0. I had to change the autofill option to something else and back again. Now looks like it's fixed. Thanks