This issue is still outstanding:
Biometric unlock is currently unavailable. Please try again later.
This issue is still outstanding:
Biometric unlock is currently unavailable. Please try again later.
I moved your post into its own thread, as it was not related to the topic from 2023 where you had commented. The error message that you have quoted has only existed in Bitwarden for less than 2 months.
A review of the source code and the pull request that created this error message suggests that the error occurs due a hardware or operating system configuration that prevents biometrics from working.
Are you able to use biometrics for other purposes on this device? Can you provide more information about which Bitwarden app you are using (including its version), as well as what browsers and operating systems are involved? What type of sensor is used to detect the biometric input?
The issue is the same as my original post.
The only thing that has changed in the last 19 months is the UI and text of the error message.
I’m using the Bitwarden add-in for Firefox on a Mac with Touch ID. I can use Touch ID for other things on my Mac and it works fine.
What version is the extension on?
And what version is your Bitwarden desktop app?
Firefox add-on is version 2024.10.0
Desktop app for mac is version 2024.9.0 (30042)
I have auto updates enabled and both appear to be the latest.
Not to belabor the point, but even though the above are the “only” changes visible to you, there have in fact been major rewrites of the biometric unlock code “under the hood” this past year. So while the end effect to you may be unchanged, the root cause (and therefore the solution) is likely to be unrelated to the previous issue — unless you are still not launching the desktop app before unlocking the browser extension (which appears to have been the cause of the original issue).
I have the same issue, running a Macbook Air M1 with Touch ID, Firefox addon version 2024.10.0 and desktop version 2024.9.0 (30042). Touch ID works for everything else.
@danstan32 Welcome to the forum!
Just to clarify an important point: Is the desktop app running when you see this error in the browser extension?
Also, I would recommend updating your Desktop app to version 2024.10.1 (just released), and seeing if that changes anything. An updated browser extension (version 2024.10.1) was also released today, although it may take a few days (or sometimes longer) before the extension update is made available in the app stores.
I’ve updated to 2024.10.1 for both the desktop app and browser extension. It only works if I keep the desktop app open. If the app isn’t open, the browser extension doesn’t even to try to open it. It also doesn’t error like before. Clicking the “Log in with biometrics” button does absoutly nothing now (unless the desktop app is open). I pretty much never use the desktop app. It either needs to work without the desktop app, or it needs to be more seamless about opening the app, getting the authentication, and closing again.
This is completely normal and expected behavior.
I would recommend that you configure the following options in your Desktop app (enabling the first 4 and disabling the 5th), which should ease your pain considerably:
If you wish for Bitwarden to implement functionality that does not currently exist, you can post a Feature Request.
There are two existing feature request topics that you may consider voting for:
I don’t like keeping the Bitwarden app running in the background at all times when I have no use for it. Why can’t the app just open when needed (to prompt for TouchID) and then close again once completed? It seems like that is how it used to work based on the behavior I showed here: Ask for biometrics on launch
Then you should support one or both of the Feature Requests that I linked above.
No, it never worked like that, and you didn’t show anything in the linked thread indicating that Bitwarden “used to” automatically launch (and close) the desktop app when unlocking the browser extension with biometrics.
Already done.
The screen recording I provided in that thread clearly shows the desktop app starting and immediately quitting in the dock. It probably wasn’t supposed to do that, but I don’t see why it couldn’t be done.