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
I've not yet found a way to reliably force this bug to occur (i.e. without having to wait), but the following steps do eventually trigger the bug for me.
Set "Start to menu bar" and open Bitwarden without logging in (alternatively set "Close to menu bar" and close the window without logging in). This bug might also occur if you leave the window open without logging in, but I haven't seen that happen myself yet.
Wait for some amount of time (it's hard to say exactly how much time, but I think somewhere around about 30 minutes).
Try triggering a global hotkey associated with a different app (e.g. the hotkey window of iterm2).
Expected Result
The hotkey triggers successfully.
Actual Result
The hotkey does not trigger and a notification is displayed saying that another app has Secure Keyboard Input enabled. Quitting Bitwarden fixes the issue.
I understand that work is tracked outside of GitHub. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
The text was updated successfully, but these errors were encountered:
Steps To Reproduce
I've not yet found a way to reliably force this bug to occur (i.e. without having to wait), but the following steps do eventually trigger the bug for me.
Expected Result
The hotkey triggers successfully.
Actual Result
The hotkey does not trigger and a notification is displayed saying that another app has Secure Keyboard Input enabled. Quitting Bitwarden fixes the issue.
Screenshots or Videos
No response
Additional Context
No response
Operating System
macOS
Operating System Version
Sequoia 15.3
Installation method
Mac App Store
Build Version
Version 2025.1.3 SDK 'main (28c7e29)' Shell 33.2.1 Renderer 130.0.6723.137 Node 20.18.1 Architecture arm64
Issue Tracking Info
The text was updated successfully, but these errors were encountered: