When copying a context or choice menu action that contains a call for dynamic JSON, the list of standard actions is omitted

Describe the bug

  1. Create a trigger.
  2. Add either "Show/Choose from List (Configurable)" or "Show Custom Context Menu (NEW)"
  3. Add some standard actions to the menu.
  4. Enable "Retrieve content dynamically..."
  5. Run trigger. The standard actions are at the top of the list, before the JSON content.
  6. Copy the action.
  7. Either paste the action or view the clipboard content. The standard action list is gone.

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

MacBook


Device information:

  • Type of Mac: MacBook M1 Pro
  • macOS version: 15.4.1
  • BetterTouchTool version: (please post the exact version - not just "the latest one")

5.397


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

Maybe I'm misunderstanding something, but it seems to work fine here. You mean it breaks if you copy & paste an action here (in the window with the "Finish Action Configuration" button?)

If you hit Copy in the screenshotted context, on a menu action that contains menu items (e.g. those in the upper right corner), then the resulting clipboard contents do not include the menu actions. Only the contents of the "Retrieve content dynamically via Javascript / JSON" field.

It's actually more troublesome than I thought. I initially blamed the "Retrieve contents dynamically..." checkbox for "overriding" the menu contents. But it appears they are omitted regardless of whether it's active or not.

This really threw me off several times, when I was first experimenting with the "Prompt with list" tutorial preset. After I customized my own menu, I copied it to another trigger. Since the dynamic script field remains populated, it's easy to not notice at first that all your menu items are gone.

There's no obvious visual cue that the menu action is empty, and when you invoke the menu, it's populated with your dynamic list items. Took me a little while to even figure out at what point they'd disappeared.

Can you check whether this is fixed in 5.398 alpha?

Fixed. Thanks the (very!) speedy response.