fix 🐛: force iMessage service on buddy-based sends to prevent SMS fallback

[Micah Goulart (mgoulart)]

Problem

When calling sdk.send(recipient, text) with a phone number or email, messages are sent as SMS (green bubble) instead of iMessage (blue bubble), even when the recipient supports iMessage.

The root cause is that generateSendTextScript and related buddy-based send helpers use a bare buddy lookup with no service specified:

tell application "Messages"
    set targetBuddy to buddy "+1234567890"
    send "Hello" to targetBuddy
end tell

On Macs where both iMessage and SMS relay are active, Messages resolves the buddy against whichever service is the default — often SMS.

Fix

Explicitly resolve the buddy against the iMessage service in all four buddy-based send helpers:

tell application "Messages"
    set targetService to 1st service whose service type = iMessage
    set targetBuddy to buddy "+1234567890" of targetService
    send "Hello" to targetBuddy
end tell

Affected functions

• generateSendTextScript
• generateSendWithAttachmentScript
• generateSandboxBypassScript (file attachment helper)
• generateDirectSendScript (file attachment helper)

Chat ID-based sends (generateSendTextToChat etc.) are unaffected — they use chat id "..." which already resolves the correct service.

Testing

All 283 existing tests pass. Manually verified blue bubble delivery on macOS with SMS relay enabled.

Closes #39

[Copilot]

Pull request overview

This PR updates the AppleScript generators used for “buddy”-based sends so Messages resolves recipients against the iMessage service explicitly, preventing unintended SMS (green bubble) fallback on systems with SMS relay enabled.

Changes:

• Force iMessage service resolution in generateSendTextScript.
• Force iMessage service resolution in attachment send helpers (direct send + sandbox bypass).
• Force iMessage service resolution in text+attachment combined send helper.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.