You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When asking to unlock a vault from the extension will the desktop app is running in the background, the Vault Unlock popup window will appear in the desktop app, but it will be empty, i.e. the passwprd field is absent.
I'm still trying to figure out how this happens, I've seen it twice today. After restating the desktop app, I was unable to reproduce.
The text was updated successfully, but these errors were encountered:
I think I found it. The desktop app must be running in the background, but the main window must be closed. When asking to unlock a vault from the extension, the desktop app's main window will appear with the empty popup. Even if we close the popup but keep the main window opened, asking to unlock a vault from the extension will continue to pop up an empty Vault Unlock.
If the desktop app's main window is opened by the desktop app (app icon > open or clicking the desktop app icon in the taskbar or in the app menu), the Vault Unlock popup is properly displayed.
Another clue seen from Windows which wasn't visible under Linux: when the empty Vault Unlock appears, there is in fact two main windows (for some reason, under Linux, there is only one visible main window, which may have to do on how the OS handles app which can be run once).
Oxalin
changed the title
Asking to unlock a vault from the extension sometimes opens an empty Vault Unlock popup
Asking to unlock a vault from the extension while the desktop app is running in the background opens an empty Vault Unlock popup
Apr 1, 2024
Extension 3.1.0
Desktop app 2.26.5
When asking to unlock a vault from the extension will the desktop app is running in the background, the Vault Unlock popup window will appear in the desktop app, but it will be empty, i.e. the passwprd field is absent.
I'm still trying to figure out how this happens, I've seen it twice today. After restating the desktop app, I was unable to reproduce.
The text was updated successfully, but these errors were encountered: