Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
macOS 10.15.1 crash in obs_hotkeys_platform_is_pressed() when interacting with password prompt #2292
It shouldn't crash
It crashes in
Steps to Reproduce
The same crash also happened in other situations where I wasn't interacting with a password prompt, but I can't tell what triggered it.
I'm also experiencing this issue (same call stack) on Catalina when interacting with a CEF-based OBS plugin.
Temporary workaround: disable input monitoring permission in system preferences / security and privacy. Guessing this is related to input monitoring vs OS-level secure input on password fields, which I believe prevents input monitoring when it comes to password fields.
I've been having a similar issue myself today and thought it was weird that the specific issue above was happening but in different circumstances, I've done some testing and I am fairly sure the issue above has nothing to do with password entry as it also happens in Touch ID, and my little experience of dabling with macOS development I know there is a Secure Keyboard Entry mode which is enabled in certain situations.
This can also be manually enabled in Terminal.app, per my above ticket #2605 you'll see that various applications which I know for a fact to all use Secure Keyboard Entry are causing this.
How do you know if an application is using Secure Keyboard Entry?
I use an app called TextExpander which flags when this is enabled too long and thus why I know 1Password, Chrome, Keychain Assistant and Terminal.app (in
Given the above it seems like the issue as others have mentioned is with the OS security extensions, and basically seems like OBS is trying to communicate with one of these APIs for OS access when the Secure Keyboard Entry mode is disabled, this is not allowed by the OS, and crash?
Jim has pushed a temporary fix which will be available when we release 25.0.x to macOS.
We will keep this issue open until a proper solution (where we don't have to fully disable hotkeys) is devised. The general recommendation as far as we can tell would be to use a newer API like this, which I assume would require a fair bit of work.