[dapi]

Problem

tgcli send text|photo|file --schedule <iso> returned a message id but delivered the message immediately. Found on 2026-11-02: a message meant for 09:00 next day went out at once (also reproduced with Saved Messages).

Cause

mtcute's high-level sendText / sendMedia read schedule (Date, or a number in milliseconds), not scheduleDate. buildTextSendParams / buildMediaSendParams set params.scheduleDate, which mtcute ignores. The raw TL messages.sendMedia request legitimately uses scheduleDate and is unchanged.

Fix

params.schedule = new Date(scheduleDate * 1000) (resolveScheduleDate yields unix seconds; a bare number would be read as ms and land in 1970).

The existing tests asserted the wrong param name ({ scheduleDate }), which is why this was never caught; they now expect { schedule: Date }.

Verification

• npx vitest run tests/send-messages.test.js: 54 passed.
• End-to-end on a real account: see the comment below.

🤖 Generated with Claude Code

[dapi]

End-to-end check on a real account (owner on office3 running this branch, release 2.11.0-local-091ecc51613d): send text --to me --schedule <now+2min> returned scheduled id 3 and the message was absent from regular history; it was delivered at 18:13:46 UTC, i.e. at the scheduled time. Before the fix the same command delivered at once.