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

debug: log response structure and try multiple access patterns

Browse Source
This commit is contained in:
admin
2026-05-05 13:49:44 +00:00
Unverified
parent f6d470c51c
commit 98b8d0cca8
1 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -58,12 +58,14 @@ export async function sendStreamingMessage(ctx, text, options = {}) {
// Send initial placeholder message using ctx.api.sendMessage directly
const sentMsg = await ctx.api.sendMessage(ctx.chat.id, '⌨️ ⌨️', { parse_mode: 'Markdown' });
logger.info('📡 Full response:', JSON.stringify(sentMsg, null, 2).substring(0, 500));
// Log response structure
logger.info('📡 Response typeof:', typeof sentMsg);
logger.info('📡 Response keys:', Object.keys(sentMsg || {}).join(', '));
logger.info('📡 sentMsg keys:', sentMsg ? Object.keys(sentMsg).join(', ') : 'null');
// The Telegram API returns a response with numeric keys mapping to property names
// We need to access sentMsg['message_id'] directly
const messageId = sentMsg?.['message_id'];
const chatId = sentMsg?.['chat']?.['id'];
// Try different access patterns
const messageId = sentMsg?.['message_id'] || sentMsg?.message_id || sentMsg?.[0]?.['message_id'];
const chatId = sentMsg?.['chat']?.['id'] || sentMsg?.chat?.id || sentMsg?.[0]?.['chat']?.['id'];
logger.info('📡 Extracted Message ID:', messageId);
logger.info('📡 Extracted Chat ID:', chatId);