New Groups behave like Triggers

Describe the bug
When you create a new group, it will "Absorb" the first trigger dropped in it.
i.e., the group itself BECOMES the trigger.

Affected input device (e.g. MacBook Trackpad, Magic Mouse/Trackpad, Touch Bar, etc.):


In the screenshot below, the first 3 groups are New Groups (bugged) and last 3 groups are Old Groups (not bugged).

First 3 groups shows Missing "Notes:Group" field behavior and have ability to select a trigger for the group itself (instead of showing "Group:Group").

If another trigger is dragged inside the empty group, then the group will "absorb" the trigger (i.e. trigger disappears and group "inherits" trigger action). This is evidenced by the first group on the list below.

Device information:

  • Type of Mac: Macbook Pro 2021 16" M1 Max
  • macOS version: 14.2 (23C64)
  • BetterTouchTool version: 4.363

Additional information (e.g. crash logs, related issues, etc.):

Noticed this about a week ago, but not sure for how long it has been happening.

Could you check whether 4.364 alpha fixes this for you? (I'm not using this view mode very often, thus I think I missed that bug)

The alpha is uploading now and should be available in a few minutes.

Thank you. Almost there :sweat_smile:.

The actions field now gets populated with the group name, which can be quite distracting:

Before it just used to say "Group:Group", though honestly it would be even better if it said nothing at all and was just clear:

There also appears to be other behavior that has changed? I mean, I immediately noticed some things had stopped working and troubleshoot it thusly:

  • Triggers that share the same input but are assigned to both ALL and a Specific Application are running together (twice).

e.g., F1 is set to Dim Screen on both ALL and a Specific App, it runs twice.

  • Similarly, if there is a shared trigger that is turned ON in ALL but turned OFF for a Specific App, neither trigger will run (expected behavior: the one in ALL should run).

Ah the action / group display thing I accidentally changed with the fix. I'll change it back :wink:

The other things you mentioned can not be related to this - they sound quite weird as the app specific overrides are some of the core behaviors in BTT that shouldn't have changed in quite a while. I tried to reproduce them but it seems to work fine here. If you still encounter this it would be great if you could go to help => export diagnostic debug information and send the result to

Sorry, I mispoke last time. It's not a matter of a specific application, but rather a matter of Conditional Groups. So my original troubleshooting description should have read:

  • Triggers that share the same input but are assigned to both ALL and a Conditional Group are running together (twice).

Anyway, I have sent you the Debug info. You will note:

  • I am pressing F4 and F5, which are activating twice (once for ALL and once for the Conditional Activation).
  • I am also prssing F10, which is deactivated in the Conditional Group, but activated in ALL. Neither run (Expected Behavior: ALL should run).

Let me know if you need anything else!

Thanks Andreas and Happy New Year to you and yours :slight_smile:

unfortunately I'm not yet able to reproduce and I still wonder how such behavior could happen because BTT can only execute one action sequence on a specific trigger. I could imagine it could somehow be related to long/short presses - as these would be interpreted as two separate triggers.

Can you point me to the problematic CAGs in your setup? Then I might be more lucky looking at your setup. Is it a specific type of action you are triggering?

I'm not 100 % sure I understood correctly, however a CAG (or normal app) always overrides what is set in "all apps". So if you have F10 in "All Apps" and your CAG is active AND also contains F10 but has it disabled - then the disabled F10 would override the "All Apps" F10.

Yes, I do have short/long presses set up for these keys. I sent you a video I had recorded earlier so you can see the issue and the specific CAG. Hope it helps.

As for the second part, I guess I was mistaken about the deactivated trigger override! Sorry about that. I could've sworn that wasn't the case, but if you're saying it is then that is that! :sweat_smile: