Additional information (e.g. StackTraces, related issues, screenshots, workarounds, etc.):
BTT used to work properly, I’ve only seen that behavior recently—though I can’t pinpoint exactly when this started happening. Also, sometimes BTT starts working by itself within a couple seconds, other times I have to lock/unlock the MBP for BTT to start working again.
unfortunately not really. macOS does have a function to retrieve the app that enabled secure input (and forgot to disable it), but that function is unreliable and buggy. Especially if it shows "loginwindow" this basically means nothing - it could have been any app in that case.
Possibly try upgrading to 12.3, Apple has fixed an issue related to the login window there - but I do not know whether it is relevant to this issue.
The interesting thing here is that I have other apps that define global keyboard shortcuts (for example: MonitorControl, to adjust the brightness of secondary monitors), and the assigned shortcuts for those apps still work correctly when BTT is displaying its warning message in the menu about Secure Input. This is why I assumed it was a problem specific to BTT.
Standard shortcuts will continue to work with secure input, but BTT is using more advanced techniques for special shortcuts which wouldn't be possible otherwise (e.g. key sequences, shortcuts including FN and many more)
Oh I see, true, FN shortcuts are only possible in BTT (I think).
I hate those bugs. The only option now is to eliminate apps one by one, and since this is intermittent on resume from sleep this gonna take ages. Urgh.
No, only the app that has enabled Secure Input can disable it again. Password managers should only enable it while you enter some sensitive data and disable it afterwards - if Bitwarden doesn't do that correctly you should report it to them.
While it has not been an issue before (I have been using BTT for at least two years), I am seeing this a lot these days, and it is not related to Sonoma because, on my Mac mini, I am still on Ventura.
It seems strange that there is no way of tracing back which app activated the secure input. Doesn't the very notification "Secure input activated by: loginwindow (PID: 173)." provide a hint?
What does "loginwindow" refer to? I initially understood it as referring to the macOS Login screen, but that doesn't make sense. What other "loginwindow" is there?
I have also been hitting this occasionally in Ventura. I agree that it seems to be happen after waking from sleep (so the login screen is the culprit.) I find I can clear it up by just opening the BTT configuration window.
I seem to remember that the issue came and went away multiple times during one login session, but I may well be wrong about that.
I will try both, though I can’t really see how BTT can clear the login screens secure input when only the app that initiated secure input can turn it off. Are you sure what you’re clearing is secure input from “loginwindow”?
Hey, even with Sonoma 14.4.1 on M1 it is still an issue, happened right now to me. Rebooting is annoying tbh because 200 browser Tabs are open :-/ Any idea if this can be solved somewhere soon?
It needs to be solved in the app that forgets to deactivate Secure Input. Unfortunately due to a macOS limitation BTT can only guess which app was responsible for activating Secure Input. Often you can figure it out by trying to remember which app presented the last password input box. Restarting that app usually fixes it.
Thank you for the quick reply. I will try to do so but I have a company administered Mac with some self-developed security tools that sometimes lock the input. Anyway, great Tool and I can't imagine using my Macs without it!
ah understood! In that case you will run into issues a lot unfortunately. There is no way to get around secure input mode (that would defeat its purpose), thus BTT can only support standard keyboard shortcuts if secure input is active ;-(
