Describe the bug
BTT keeps getting stuck in a disabled state since upgrading to Sonoma. I've tried enabling both settings related to secure input, but it stills ends up disabled with either and both enabled.
Usually it's just the keyboard shortcuts that are disabled. Though a few times something has gone wrong with the touchpad input as well where that seems to also be in a disabled state and I am unable to click until quitting BTT.
I've tried isolating which app might be causing secure input to be triggered. It seems like it might be Chrome. But I'm not entirely sure about that. Let me know if there's a way to diagnose that better. Also if there's any way to get logs from BTT related to when it is disabled.
A clear and concise description of what the bug is. Any bug reports that contain insults against me or my software will be deleted without warning (unfortunately this has become necessary to mention here).
Affected input device (e.g. MacBook Trackpad, Magic Mouse/Trackpad, Touch Bar, etc.):
Keyboard
Sometimes trackpad
If you have given the Accessibility permission (which is important for BTT), the Input Monitoring is not necessary and can even cause some issues
BTT will automatically try to remove the input monitoring permission when it starts.
Interesting, so far the input monitoring permission hasn't been removed (tried restarting a few times). Accessibility permission is also granted. I've unchecked the input monitoring permission and will see if the issue reoccurs.
I am having as best I can tell the exact same issue.
Type of Mac: Macbook Pro 14-inch, 2021 with Apple M1 Pro
macOS version: macOS Sonoma 14.1.1 (23B81)
BetterTouchTool version: 4.318 (43180) (Regular release channel)
I also checked and I did not have anything disabled under Global (App specific settings). I have removed and re-added the accessibility permission without any improvement.
@Andreas_Hegenberg I think you've identified the trigger. I'm running Sonoma on a M1 Air.
For the options
Restart BTT after wake from sleep
Enable sync
If I disable either of these (or both), I get expected behavior / not stuck in disabled mode after sleep.
With both enabled (my existing config) I can reliably reproduce "disabled after sleep" on BTT 4.318 and 4.321
EDIT: When I disable "Restart BTT after wake from sleep" I intermittently get issues after resuming (which is why I had turned it on in the first place). But this is not every time I resume, and not as obvious -- the BTT menu doesn't indicate it's disabled, but my hotkeys don't trigger.
Having the same issue, I'll try disabling sync + restart from sleep. It started happening for me with the last OS update.
Also as a possibly related note I noticed when BTT was disabled keyboard input was a bit weird, in that keypresses would go missing. I thought it was me, but apparently something was eating keyboard input?
Nope. Now whenever it loads, it immediately grays out and says "BTT is currently disabled. See below." (I'm not sure what the see below is referring to.). I've sent my logs to you, Andreas.