After updating to the latest version, including Alpha. BTT quits on sleep. I have to start it every time macOS wakes up.
Version 3.581 (1724)
Note: Before bug reporting, please make sure you have tried the latest (alpha) version of BetterTouchTool and that you have already tried to restart your system :-). If you encounter a crash, please attach a crash log from the macOS Console.app from the "User Diagnostic Reports" section.
Describe the bug
A clear and concise description of what the bug is.
I've recently switched to an M1 Macbook Pro from an Intel machine; BTT was pretty solid on the Intel machine but crashes regularly on the M1 - it seems I'm seeing this 'crash on sleep' behaviour? (though my mac doesn't sleep, it's always powered on; display off only). Basically, I log in from the display lock and BTT's gooooone.
Are there any kind of logs I can gather?
(also on Version 3.581 (1724); macOS 11.6 (20G165)
I'm seeing similar - btt very regularly not present after a wake. This is on iMac Pro (Monterey beta) and M1 MBP 13" (Big Sur). It's been happening for at least a couple of months - I didn't log it as I only saw it on the Monterey beta, and expected that you'd get around to it in the usual way. But now I've got the M1 and I've been seeing it on Big Sur there as well occasionally. For me it's much worse on the Intel/Monterey than on the M1/Big Sur.
I've got very quick at cmd-space-be-enter, but it's not ideal
BTT v 3.581
+1 on this. I'm using an iMac with OS 11.6 and BTT 3.581. This either started happening because I recently upgraded to 11.6 (from Mojave) or to this latest BTT at around the same time. I should mention that I have tried the "Restart BTT after wake from sleep" option both checked and unchecked, and there is no difference.
This will be fixed in the next release (which still takes about a week because it contains many new features related to the new shortcuts app on monterey)
Yes, I've always had "Restart BTT after wake from sleep" enabled. I forget why now, but it may have been from something that was happening like five+ years ago!
On the plus side, I've not seen this problem in 3.600 or 3.602 on Intel or M1. Fingers crossed you've nailed it