When a trigger is disabled, it can still affect other triggers.

Bugs or Unexpected Behavior
1

The first scenario:

image
image778×208 25.3 KB

Finder can't be triggered normally, but if only one exists or a different shortcut is set, it works fine.

The second scenario:

image
image782×110 7.49 KB

image
image776×116 10.2 KB

Type the phone number; it's a key-sequence trigger set to “;17”, but as long as the trigger above exists, it won't work.

Device information:

  • Type of Mac: M1
  • macOS version: 15.7
  • BetterTouchTool version: 5.649
2

I just realized the second issue happened because I had set a key mapping—mapped 1 to “no key.” However, the "Reset All Low Level Keyboard Key Remappings" action cannot restore it. I can still see it in the records:

image
image640×160 20 KB

If I manually remap 1 to 1, 70000001e disappears.

3

unfortunately I can not reproduce this.

Could you copy & paste those two triggers here? (cmd+c / cm+v)

4

The first scenario:
I used a simpler method to reproduce it. Whether by copying or manually creating a trigger, any previously created trigger stops working. In this example, Mission Control was created previously—enabling it alone has no effect, whereas enabling Launchpad alone works. If both are enabled and you choose via the menu, either one can trigger.

image
image712×198 16.5 KB

[
{
"BTTLastUpdatedAt" : 1758668374.60425,
"BTTTriggerType" : 0,
"BTTTriggerClass" : "BTTTriggerTypeKeyboardShortcut",
"BTTUUID" : "375988C4-EF08-4ACB-80D4-E2D78D7B1A1D",
"BTTAdditionalConfiguration" : "524352",
"BTTShortcutKeyboardType" : 2302,
"BTTTriggerOnDown" : 1,
"BTTLayoutIndependentChar" : "z",
"BTTShortcutKeyCode" : 6,
"BTTShortcutAdvancedModifierKeys" : "524352",
"BTTShortcutModifierKeys" : 524288,
"BTTOrder" : 19,
"BTTAutoAdaptToKeyboardLayout" : 0,
"BTTActionsToExecute" : [
{
"BTTLastUpdatedAt" : 1758667507.8569989,
"BTTTriggerParentUUID" : "375988C4-EF08-4ACB-80D4-E2D78D7B1A1D",
"BTTIsPureAction" : true,
"BTTTriggerClass" : "BTTTriggerTypeKeyboardShortcut",
"BTTUUID" : "264B61B0-5048-4B66-9FE3-DEC2E0ECD331",
"BTTPredefinedActionType" : 5,
"BTTPredefinedActionName" : "Mission Control",
"BTTShortcutKeyboardType" : 0,
"BTTShortcutKeyCode" : -1,
"BTTOrder" : 2,
"BTTAutoAdaptToKeyboardLayout" : 0
}
]
},
{
"BTTLastUpdatedAt" : 1758668729.6982141,
"BTTTriggerType" : 0,
"BTTTriggerClass" : "BTTTriggerTypeKeyboardShortcut",
"BTTUUID" : "F2B18F03-48F3-4FD2-A08E-F064D8A63720",
"BTTAdditionalConfiguration" : "524352",
"BTTShortcutKeyboardType" : 2302,
"BTTTriggerOnDown" : 1,
"BTTLayoutIndependentChar" : "z",
"BTTEnabled" : 0,
"BTTShortcutKeyCode" : 6,
"BTTShortcutAdvancedModifierKeys" : "524352",
"BTTShortcutModifierKeys" : 524288,
"BTTOrder" : 20,
"BTTAutoAdaptToKeyboardLayout" : 0,
"BTTActionsToExecute" : [
{
"BTTLastUpdatedAt" : 1758667861.4723868,
"BTTTriggerParentUUID" : "F2B18F03-48F3-4FD2-A08E-F064D8A63720",
"BTTIsPureAction" : true,
"BTTTriggerClass" : "BTTTriggerTypeKeyboardShortcut",
"BTTUUID" : "00760058-78FE-4E94-8059-37DD262FB41C",
"BTTPredefinedActionType" : 115,
"BTTPredefinedActionName" : "Open Launchpad",
"BTTShortcutKeyboardType" : 0,
"BTTShortcutKeyCode" : -1,
"BTTOrder" : 3,
"BTTAutoAdaptToKeyboardLayout" : 0
}
]
}
]

5

The second scenario:

After executing "Reset All Low Level Keyboard Key Remappings," key code 70000001e isn't removed—you have to remap it manually to restore the original key. Is this the expected behavior? If so, I'll have to go through and remap each key one by one to fix the issues caused by triggering the keyboard key remap.
By the way: When you haven’t remapped the key to the original key, and you disable the whole group instead of a single trigger, that trigger will still show up in Resently Used.

6

The reset action will only reset keys if they are no longer configured in BTT, otherwise they will reset but immediately re-configure

Unfortunately I still can't reproduce your disabling issue. Maybe you could go to help→ export diagnostic debug information and send the result to andreas@folivora.ai

7

Oh, I’ve found a more specific cause: when I use the conditional activation group on the left, the issue is reproduced, but globally it behaves normally.

8

Ah perfect, there I can reproduce the issue. I’ll check whether I can fix that.

//edit: however it only seems to fail while I’m still in the BTT UI. If I switch to another app it works correctly. Is that also the case for you?

9

Yes, but switching to another app only works once—after that, it fails again.

10

Found the issue, fixed in 5.660! Thanks for reporting!