@PhilG There are definitely lots of things in motion! The status page has the issue posted. It’s not a ‘current’ issue since it has been resolved in client updates.
As for backout/rollback/etc - the app stores don’t have any forceful mechanism to change clients on consumer’s devices (for good reason of course) - you must go forward, and it just takes a little bit of time for those updates to be tested, submitted, approved, and then actually applied to your browser.
The latest revision 15.3 seems to have fixed it with Chrome. You must go back in and set the timeout to NEVER if you had it set that way before.
I have the latest version (1.56.3) and am still unable to stay logged into BW via the Chrome extension, or access any vault entries, though accessing via the web or Firefox extension works normally.
Thanks David,
It is now showing v1.56.3 and also working properly. So, I guess it must have updated automatically.
Thanks again to the Bitwarden team.
I can confirm that both the Chrome browser and the Windows desktop app are back to normal. Thanks for the hard work in getting this solved!
I’m only seeing a 1.55.0 for Firefox.
@tgreer in this case may i respectfully suggest a couple of things?
change the status page so people can see/understand what’s going on in a single place, without having to go to different threads?
include information about github, so people can get the issue fixed without the additional delay of getting the new revision to the chrome (or other for that matter) store?
Please add the already reported issue with the Chrome console warnings to your list of known issues: Can’t load source maps cluttering console
Windows 10 x64
Chrome Version 98.0.4758.82 (Official Build) (64-bit)
Bitwarden Version: 1.56.4
It is already in the first post! 
Doh! I even saw that and give a hearts-up <3 before I posted that reply. 
Sorry if I missed it but did 1.56.4 also fix the auto lock issue? (Bitwarden locking regardless of timeout settings)
One person reports that it did, although they did say you had to set the Vault Timeout = Never, and after that it would work and you can presumably pick another setting:
Has anyone been able to resolve the “keeps asking for master even when you’ve selected never” issue on Brave?
I have found that the issue is not resolved by simply updating the extension and restarting the browser. The next step of advice calls for uninstalling the plugin, logging out of Chrome, and then reinstalling after a restart. However, even though Brave is Chrome-based, it uses a blockchain-based mechanism for sync, and does not have a concept of “logging out”.
I was on 1.56.4 on Chrome and it was still locking (setting set to “On browser restart”). Noticed just now that it’s been updated to 1.56.5 so I’ll see if it happens again. Perhaps I was already on 1.56.5 and it locked again…
Try this:
And if necessary, also try this step posted as a solution by @ConsistentCorgi below:
Hope that works!
EDIT: added one more step by @ConsistentCorgi
Thanks, but no change…
Browser integration is not enabled
Browser integration is not enabled in the Bitwarden Desktop application. Please enable it in the settings within the desktop application.
Not sure then - it could be an issue with Windows Hello. You might go back to the installation instructions here and ensure that you did it all correctly:
Read the info under both the Desktop and Browser Extension tabs. Make sure that biometrics are working on the Desktop App before trying to enable on the FF extension.
And you might want to review this if you can’t get biometrics working on the Bitwarden desktop app:
@dh024 I’m having the same problem with Biometric login as Ron_B above. I initially had a slightly different issue - getting the error message “Start the Bitwarden Desktop application. The Bitwarden Desktop application needs to be started before this function can be used”, when trying to unlock with Biometric (despite the desktop app already being open).
So I uninstalled and reinstalled the extension, uninstalled and reinstalled the desktop application like you described above, and enabled biometrics + browser integration in the desktop app. Up to now, all good; I can unlock the desktop app with Windows Hello. But when I try to enable Biometric in the extension, I get the “Browser integration is not enabled” error message.
Edit: Problem seems to have been solved by ticking the additional box “Require verification for browser integration” in the desktop app. I never had this checked in prior versions do didn’t think of ticking it, but after ticking it now the browser extension biometric unlock seems to work fine!
I’m in the same case than @ConsistentCorgi . For a week now I’m getting “Start the Bitwarden Desktop application” whereas it’s fully started.
It’s probably due to last updates… is there an official solution? Uninstalling/installing both application and extension does not seem a good way to me…
Thank you,
