[BUG] typing command fails with 'any;-;' chat identifier prefix

[claww13]

Description

imsg typing fails with "Chat not found" when the chat.db uses any;-; prefix instead of iMessage;-; in the chat identifier/guid.

Steps to Reproduce

1. Have a chat where the DB stores any;-;+phonenumber as the guid (common on Apple Silicon Macs)
2. Run: imsg typing --to +phonenumber --duration 3s
3. Also fails with: imsg typing --chat-id 2 --duration 3s

Expected

Typing indicator should work regardless of the service prefix in the chat identifier.

Actual

typingIndicatorFailed("Chat not found for identifier: iMessage;-;+971565061013. Make sure Messages.app has an active conversation with this contact.")

Investigation

The DB has:

SELECT ROWID, chat_identifier, guid FROM chat;
-- 2|+971565061013|any;-;+971565061013|iMessage

But the typing command constructs iMessage;-;+971565061013 when looking up the chat in IMCore. AppleScript confirms the chat exists as any;-;+971565061013.

Note: imsg react works fine on the same chat (uses different lookup mechanism).

Environment

• imsg v0.5.0
• macOS 15.3 (Sequoia) arm64
• Messages.app running with active conversation

[sihly]

+1 on this — same issue here (macOS 15.3, arm64, imsg 0.5.0). All my chats use the any;-; guid prefix.

Interestingly, imsg react --chat-id 1 -r love reports success but the reaction doesn't actually land on the correct conversation. It appears to react to whatever conversation is currently visible in Messages.app rather than the specified --chat-id. The CLI returns {"success": true} but the reaction either goes to the wrong chat or doesn't register at all. So both typing and react seem affected by the any;-; lookup issue — just failing differently (typing errors out, react silently targets the wrong chat).