Failed unlocking source: Source in invalid state (unlocked)

[eandersons]

I am getting the following error when I try to unlock the vault:

Failed unlocking archive Unable to unlock archive (...): Unlocking archive source (...) failed: Failed unlocking source: Source in invalid state (unlocked): ...

In form fields dialog it seems that the vault is unlocked (there is no button to unlock vaults), bet there are no entries. In browser extension icon dialog the vault has a keypad icon.

Details:

• OS: macOS Catalina and Windows 10
• Browser: Firefox Developer Edition (64-bit)
• Extension version: 2.19.0

I am not sure but I think that I have observed the same error on Windows 10 and Firefox Developer Edition as well. It seems that this error occurs after computer has been put to sleep or hibernation for a while but I am not completely sure about it.

The vault can be unlocked after the extension has been disabled and reenabled.

I am happy to provide additional details if needed.

[ivanovd]

Same here with Edge Chromium v. 85.0.564.23 on Windows 10 Pro build 19041.423

[erineldridge]

I've run into this as well and wanted to emphasize this: it seems through interacting from the user-side that the "try to unlock the vault" code and the "what vaults can I interact with" code in Save Credentials page (sorry I'm sure I'm not using any of the right jargon here) disagree on which vaults are unlocked, and the Save Credentials page is the one that's correct as far as I can tell.

[xakraz]

Hi there!

I am facing the exact same issue:

Failed unlocking source: Source in invalid state (unlocked)

📝

• OS: macOS Mojave 10.14.6
• ButterCup extension: 2.24.3
• Browser: Google Chrome 101.0.4951.54

📝 (2) I am able to unlock the exact same vault using the desktop version (2.14.2) and mobile version (Android, 2.4.2). The storage backend is Google Drive.

[xakraz]

Edit: Finally it works again ....

And like other issues with Chrome (stuff that stop working), the browser was in the middle of an update. After restarting the browser, everything was back to normal.

Sorry for the noise 😅 but very user-friendly for people not used to these Chromeish issues.

[perry-mitchell]

Closing this as the new V3 release renders this issue as either outdated or irrelevant. If you feel this was in error, please don't hesitate to comment. Please note that you should, at very least, test again in the new release once it's out.