When a bot sends a sendChatAction request with message_thread_id set to a private DM topic (not a supergroup/forum), the typing indicator appears in the parent / "New Chat" view instead of inside the active topic on macOS and iOS clients.
The same bot call renders correctly inside the topic on Telegram Desktop (Linux/Windows) and Telegram Web.
Steps to Reproduce:
Create a bot and enable DM topics with your account
Open a DM topic with the bot in your Telegram app on macOS or iOS
Send a message to the bot to trigger a response
Observe the "typing…" indicator — it shows in the parent DM chat header, NOT inside the topic thread
Repeat the same conversation on Telegram Desktop (Linux/Windows) — the typing indicator correctly appears inside the topic
Technical Details:
The bot calls sendChatAction with both chat_id (user's numeric ID) and message_thread_id (the DM topic's thread ID). The Telegram Bot API returns success (HTTP 200), and the server-side routing is correct — messages from the bot do land in the topic. However, the typing indicator is rendered at the parent chat level on Apple clients.
This does NOT apply to forum/supergroup topics, where message_thread_id works correctly across all platforms. The issue is specific to private DM topic lanes.
Expected Behavior:
The typing indicator should appear inside the active DM topic thread on all platforms, matching the behavior of regular bot messages.
Actual Behavior:
On macOS and iOS, the typing indicator appears in the parent/new-chat view instead of the topic. On Desktop (Linux/Windows) and Web, it renders correctly inside the topic.