admin/zCode-CLI-X
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: use ctx.api.sendMessage instead of ctx.reply for streaming

Browse Source
This commit is contained in:
admin
2026-05-05 13:45:45 +00:00
Unverified
parent f8a6edf4c7
commit e839f513de
1 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
src/bot/message-sender.js
View File

@@ -55,13 +55,13 @@ export async function sendStreamingMessage(ctx, text, options = {}) {
try { try {
logger.info('📡 Starting streaming for message of length:', text.length); logger.info('📡 Starting streaming for message of length:', text.length);
// Send initial placeholder message // Send initial placeholder message using ctx.api.sendMessage directly
const sentMsg = await ctx.reply('⌨️ ⌨️', { parse_mode: 'Markdown' }); const sentMsg = await ctx.api.sendMessage(ctx.chat.id, '⌨️ ⌨️', { parse_mode: 'Markdown' });
logger.info('📡 Initial message sent:', JSON.stringify({
message_id: sentMsg?.message_id, logger.info('📡 Reply response type:', typeof sentMsg);
chat_id: sentMsg?.chat?.id, logger.info('📡 Reply response keys:', sentMsg ? Object.keys(sentMsg) : 'null');
full_obj: Object.keys(sentMsg || {}) logger.info('📡 Message ID:', sentMsg?.message_id);
})); logger.info('📡 Chat ID:', sentMsg?.chat?.id);
// Extract IDs safely // Extract IDs safely
const messageId = sentMsg?.message_id; const messageId = sentMsg?.message_id;