Bitwarden extension for Firefox no longer working with bio-metrics or PIN

Agreed. That is not a solution just a temp workaround.

The last time a password software company dragged their feet like this, kept their users in the dark like this, and kept insisting everything was all right…
was Lastpass. We all should remember how many users they lost, but more importantly the damage it did to their reputation will be felt for years. History has shown more companies suffer reputational damage by how they respond to events that effect their customers. Sad to see it happen!

1 Like

Hi @discomBOBulate and others, The Firefox client update process certainly needs work and the team identified a situation missed in recent releases. This has now been addressed. Bitwarden is thankful to have everyone as users and is appreciative of the patience working through this. Please stay tuned for the next client update.


Also waiting for a fix. Using latest version of Firefox on Ubuntu Linux.
Keeping an eye on for a new published version.

v2023.8.3 is no good.

1 Like

"This topic has been solved’

It will be when we finally get the new version from Mozilla, till then this remains a problem for we users don’t you think.

You probably know this already but I’ll write it just in case - you can always disable last version which will prevent users from auto-updating to it. And new users will be able to install the previous versions. So only those that already updated will be affected.

Heck you haven’t even removed it from the add-on site to prevent additional downloads.
Haven’t requested an emergency review by AMO admins.


Firefox Addon version 2023.8.3,

Desktop Version
Version 2023.9.0
Shell 24.8.3
Renderer 112.0.5615.204
Node 18.14.0
Architecture x64


Windows 11 Pro
Version 22H2
Betriebssystembuild 22621.2361
Windows Feature Experience Pack 1000.22674.1000.0

works here perfectly again.
Only had issues Addon version 2023.7.1. when it wasn’t upgraded along the desktop version.

Greetings Kalle

I have been away for a few days.
FF Add on is still 2023.8.3. Desktop Version is 2023.9.0 now. I updated manually today. Before the update didn’t succeed, or wasn’t available? (Yet announced).
Unlike Kalle73kw, I am on Windows 11 Home (fully patched), not Pro.
Here also, now all works perfectly again.

Me happy ! :smile:

Still unable to set an unlock PIN with FF Addon 2023.8.3 and Desktop 2023.91. FF is 118.0.1 (64-bit).

You can sideload version 2023.9.1 from Github.

For me it’s working with the same set-up.
Is your Bitwarden set up the right way for the PIN?

The suggestion to sideload from Github is not possible because the software is not signed. Unless I am missing something, this is not an option either. Reverting to the July version of the extension does work for PIN access. Would appreciate a clarification on if 2023.8.3 has resolved the PIN problem and if so, why hasn’t the version number updated?

Just FWIW.
A sideload works (by debugging), however no real solution. :roll_eyes:
Therefor for you and me (and more users) no solution. You are right!

As for my situation, 2023.8.3 has solved the PIN issue. Can’t say it does for everyone (see FunkyB).
On the other hand, I messed up the log-in-by-PIN-settings before, trying to solve things, so I had to correct them first.

I understand your frustration, but Bitwarden has corrected the issue. It’s up to Mozilla now to release it.

They seem to move at a slow pace.

Well, it would seem I have gotten the attention of at least two folks on this thread, but my point still stands. Taking a month (or technically 3 weeks per Go12’s post 7 days ago) to identify a problem and then supposedly issue a fix still feels like an eternity for people who pay for the use of this program and who swear by it and tell others to use it also. At this point, I really do not care if my tone and/or words have come across as rude or out-of-line. I, as a paying customer of a product and service, expect better and would appreciate the people who develop this open-source product to be more transparent. Furthermore, if there is a problem with Mozilla releasing updates, then let us know that and tell us who we can go to and complain about their broken eco-system. In the end, I just want what I am paying for to work properly and not be told to jump through this hoop or perform this action as a work-around. I personally feel Bitwarden is far better than that and that is precisely why I left another company who was not any of what I mentioned above.

Actually, there are two separate issues that have been discussed in this thread. OP’s post is in regards to Bug 6169: Biometrics Not Working On Firefox, which was first reported on September 1, and was caused in part by a mismatch between the Desktop app and Firefox extension version number when changes to biometrics functionality had been introduced in version 2023.8.2.

Later, when version 2023.8.3 was released, this introduced Bug 6286: Firefox Extension — Can’t unlock vault with PIN, which was first reported on September 14, and patched on September 20.

In both cases, delays in making Firefox users whole have been caused by the slow review process for extension releases by Mozilla.



Not a bad answer but passing the culprit (again) ? :face_with_raised_eyebrow:

The question remains: Should Bitwarden as a serious Password Manager not take up its responsibility and urge Mozilla to hurry up?
Isn’t Bitwarden in essence for safety on the internet, and not for a fancy-look?

See also : PIN Unlock in Forefox no longer working in 2023.8.3 - #25 by sjokoboy

Probably pure coincidence :innocent: , FF add on is now updated to 2023.9.1 :clap:

It sounds like Bitwarden did “urge Mozilla to hurry up”:

I am now running FF browser extension 2023.9.1 and the PIN unlock feature is working correctly again. I am not going to get into a finger-pointing war of who did or didn’t do what, but suffice it to say that problems like this should be dealt with at a much faster pace going forward, especially when it deals with the core functionality of the software vs. a cosmetic change or nice-to-have. And yes, I do understand this thread dealt with two separate problems, however, the PIN problem lasted for approximately 19 days itself (and yes, more than likely due to FF changing its codebase). I also requested greater transparency as well, not just - we are aware of the problem and are working it. Moving on.

1 Like