-
Notifications
You must be signed in to change notification settings - Fork 94
Description
Bug
Custom emoji reactions (e.g. imsg react --chat-id 1 -r π€) open the tapback menu but don't select anything. The menu just stays open.
Standard tapbacks (love, like, laugh, etc.) work correctly via number key selection.
Root cause
The custom emoji AppleScript path in ReactCommand.swift tries to keystroke customEmoji into the tapback menu:
keystroke "t" using command down -- opens tapback menu
delay 0.2
keystroke customEmoji -- tries to type emoji
delay 0.1
key code 36 -- EnterBut the tapback menu is a visual grid/picker, not a text field. There's nowhere for the keystroke to land. The emoji character gets lost and Enter closes the menu without selecting anything (or doesn't close it at all).
Possible fix
Custom emoji reactions might need to:
- Open the emoji picker within the tapback popover (if macOS exposes one)
- Use accessibility APIs to find and click the specific emoji in the sticker grid
- Or use a different UI automation approach entirely
Additional note
On first invocation, the standard reaction path can also fail if Messages.app isn't already focused on the target chat. The Cmd+F search navigation works but the delays may be too short for initial chat switching. Subsequent reactions in the same chat work reliably. Consider adding a slightly longer delay after the initial Enter (chat selection) or verifying focus before sending Cmd+T.
Version: 0.5.0 / macOS 15 (Sequoia)